This bug was fixed in the package apport - 2.3-0ubuntu3
---
apport (2.3-0ubuntu3) quantal; urgency=low
* Merge from trunk:
- apport_python_hook.py: For org.freedesktop.DBus.Error.ServiceUnknown
exceptions, add a 'DbusErrorAnalysis' field to the report which points
When writing test cases for the ServiceUnknown and NoReply variants I
realized that the stack trace for NoReply does not tell us the D-BUS
name it was trying to connect to, so for the time being we cannot
collect additional information about that. For ServiceUnknown we do know
the name though, and
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020572
Title:
Deal better with DBus.Error.ServiceUnknown errors
To manage notifications about this bug go to:
Fixed in trunk: http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/2430
** Changed in: apport (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
