Martin, I'm afraid it doesn't look like the filtering is working right
wrt crashdb reporting. This is still the second most frequent crash
reported on errors.ubuntu.com for the past day/month, which means it's
still causing users in precise to be shown a crash report dialog.
Either something more needs to be done to trap the exception in jockey
so that apport doesn't see it, or something more needs to be done in
apport to make sure this doesn't raise a crash report either, because
it's definitely still having an impact on users.
** Changed in: jockey (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734376
Title:
jockey-gtk crashed with DBusException in call_blocking():
org.freedesktop.DBus.Error.NoReply in shutdown()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/734376/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
