apport not blocking DBus no reply bug reports

Bug #1042970 reported by Brian Murray
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
High
Brian Murray

Bug Description

As requested in bug 914220 apport should be blocking python crashes that are due to clients not receiving a reply. This is working in quantal and is tested by test_dbus_service_timeout_running in test_python_crash.py. This test does not exist in precise but if you port it to precise it will fail. Additionally, these crashes are being reported on errors.ubuntu.com and taking up space in the top crashers. For example see - https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fubuntuone-installer%3ADBusException.

[Impact]
Precise users are being notified of crashes that are not useful to developers and we don't want to receive. Receiving pop-up notifications for these crash reports decreases the user experience when using precise.

[Test Case]
1) Download 'test_python_crashes.py' from this bug report
2
) Execute 'python test_python_crashes.py' in a terminal.
3) Observe a test failure:
FAIL: test_dbus_service_timeout_running (__main__.T)
DBus.Error.NoReply with a running service
4) Install apport from precise-proposed
5) run the same test and observe the test passing:
Ran 7 tests in 28.111s

OK

[Regression Potential]
It is possible that apport would not generate crash reports for other types of python crashes but based off the code change it is not likely.

Revision history for this message
Brian Murray (brian-murray) wrote :
Changed in apport (Ubuntu Precise):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
importance: Undecided → High
Changed in apport (Ubuntu):
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted apport into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apport/2.0.1-0ubuntu13 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in apport (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
C de-Avillez (hggdh2) wrote :

Confirmed issue on non-updated Precise, installed Apport from -proposed, confirmed test success. Tagging verification-done.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.0.1-0ubuntu13

---------------
apport (2.0.1-0ubuntu13) precise-proposed; urgency=low

  * apport_python_hook: Backport filtering of DBus NoReply errors from trunk.
    (LP: #1042970)
 -- Brian Murray <email address hidden> Tue, 28 Aug 2012 14:42:35 -0700

Changed in apport (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.