Deal better with DBus.Error.ServiceUnknown errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Looking to errors.ubuntu.com we get a lot of DbusException errors on some of our python services (jockey, oneconf, software-
Those bugs tend to:
- not be that useful to figure the real issue
- create lot of noise for users
- be sign of setup problem rather than software bugs
We should aim at making those bugs useful, if we can't make them useful we should stop spamming the users about them since there is no point to trigger system error dialogs when there is no visible error and when the report sent is not useful
Taking a jockey issue as an example
"Traceback (most recent call last):
File "/usr/bin/
sys.
File "/usr/lib/
self.
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
DBusException: org.freedesktop
That basically tells us the service dbus activation is buggy, but doesn't really inform us on the issue....
Things we should be able to get infos on:
- is the target service installed and available (could be a missing depends)
- is the service running or does it fail to start for a reason (is there a log we can check for details on the reason)
- your ideas...
Changed in apport (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Martin Pitt (pitti) |
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 can detect whether any .service file provides the name and whether that service is running. Retitling the bug accordingly.