This crash has been fixed as drive-by fix for bug #1982555 in apport
2.20.11-0ubuntu27.25 (focal) and apport 2.20.11-0ubuntu82.2 (jammy).
** Changed in: apport (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: apport (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1979211
Title:
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
Fix Released
Status in apport source package in Impish:
Won't Fix
Status in apport source package in Jammy:
Fix Released
Bug description:
Impact
------
As it can be seen in
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
there are thousands of crashes of this type (and multiple duplicate
bug reports for it). Instead of apport logging a failure in
/var/log/apport.log, it crashes. Fixing this bug also fixes the issue
with logging failures in the socket path (for handling crashes in
containers).
Test Case
---------
There should be no instances of
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
for the fixed version.
Where problems could occur
--------------------------
The apport binary is called by the kernel when a process crashes.
Worst case scenarios include breaking the apport binary and no problem
report is generated any more (or apport uses too much resources).
Since all the desired logs are now logged, it could increase the
amount of logs that are written (apport has some flood detection in
case a process dies constantly).
Original Description
--------------------
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu82.1, the problem page at
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/share/apport/apport", line 531, in <module>
options = parse_arguments()
File "/usr/share/apport/apport", line 463, in parse_arguments
parser.print_usage()
File "/usr/lib/python3.10/argparse.py", line 2562, in print_usage
self._print_message(self.format_usage(), file)
File "/usr/lib/python3.10/argparse.py", line 2573, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'
This bug can be reproduced by configuring the previously supported
parameters to Apport and then let a process crash (e.g. call divide-
by-zero):
```
echo "|/usr/share/apport/apport %p %s %c %d %P %E" | sudo tee
/proc/sys/kernel/core_pattern
```
So this bug is a regression of commit c320e910a516 ("Switch to using
non-positional arguments") which is a fix for CVE-2022-28658 and
CVE-2021-3899.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1979211/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
