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.
** Summary changed:
- Deal better with DbusException errors
+ Deal better with DBus.Error.ServiceUnknown errors
** Changed in: apport (Ubuntu)
Status: Triaged => In Progress
--
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:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1020572/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
