[Bug 1093365] Re: apport doesn't send crash reports to Launchpad for stable releases like some people expect
Brian Murray
brian at ubuntu.com
Mon Jun 25 13:44:50 UTC 2018
** Summary changed:
- apport annoyingly and silently refuses to upload a crash report
+ apport doesn't send crash reports to Launchpad for stable releases like some people expect
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1093365
Title:
apport doesn't send crash reports to Launchpad for stable releases
like some people expect
Status in apport package in Ubuntu:
Triaged
Bug description:
Ubuntu 12.10 amd64
apport - 2.6.1-0ubuntu9
gwibber and unity-gwibber-daemon have been crashing (segfault) over
the past few days. When apport-gtk fires up, I see the error and click
continue and then nothing happens. So next I run it from the command-
line, same behavior and no output and an exit code of 0. I try again
with apport-cli, same behavior. So next I spend 10 minutes with pdb to
find out why you're refusing to upload my crash. A normal user will
not bother with this.
I traced down the refusal to upload to the accepts() function in the
CrashDatabase class inside the file /usr/lib/python3/dist-
packages/apport/crashdb.py. The problem type is Crash and
self.options will only upload Bug and Package types:
(Pdb) p self.options
{'problem_types': ['Bug', 'Package'], 'bug_pattern_url': 'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml', 'escalated_tag': 'bugpattern-written', 'dupdb_url': 'http://people.canonical.com/~ubuntu-archive/apport-duplicates', 'escalation_tag': 'bugpattern-needed', 'impl': 'launchpad', 'distro': 'ubuntu'}
(Pdb) p report.get('ProblemType')
'Crash'
With that info in hand, I modified /etc/apport/crashdb.conf to add
'Crash' as a supported type and now I can upload the crash report.
I claim that if you're going to refuse to upload my crash report, you
owe me, the user, an exit code or error message that explains why, any
other behavior is not user friendly. In fact why even pop-up apport-
gtk at all with a continue button?
In addition, I don't understand why you're setting the upload and
uploaded file flags in this scenario, that may also be incorrect since
you never uploaded anything:
-rw-r----- 1 mfisch whoopsie 2113776 Dec 23 16:31 /var/crash/_usr_bin_gwibber.1001.crash
-rw-rw-r-- 1 mfisch whoopsie 0 Dec 23 17:10 /var/crash/_usr_bin_gwibber.1001.upload
-rw------- 1 whoopsie whoopsie 0 Dec 23 17:10 /var/crash/_usr_bin_gwibber.1001.uploaded
I am attaching a crash report for twistd that it refuses to upload and
hopefully that can be useful for testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1093365/+subscriptions
More information about the foundations-bugs
mailing list