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
      out whether any .service file provides the service it tried to talk to,
      and whether the processes for those are running. This helps to determine
      the root cause for such errors (missing dependencies, broken .service
      files, talking to the wrong bus, etc.) (LP: #1020572)
    - hookutils.py, attach_alsa(): Use alsa-info.sh when available. Thanks
      David Henningson.
    - ui tests, test_wait_for_pid(): Fix eternal hang when running as root.
    - testsuite: Fix ResourceWarnings when running with Python 3.
  * debian/control, debian/tests/control: Add gvfs-daemons as build/test
    dependency, as test_python_crashes uses it as an example for handling
    python-dbus exceptions.
 -- Martin Pitt <[email protected]>   Tue, 10 Jul 2012 14:58:45 +0200

** Branch linked: lp:~ubuntu-core-dev/ubuntu/quantal/apport/ubuntu

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1020572

Title:
  Deal better with DBus.Error.ServiceUnknown errors

Status in “apport” package in Ubuntu:
  Fix Released

Bug description:
  Looking to errors.ubuntu.com we get a lot of DbusException errors on
  some of our python services (jockey, oneconf, software-properties,
  ubuntu-sso-client, ...)

  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/jockey-gtk", line 418, in <module>
      sys.exit(u.run())
    File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 470, in run
      self.backend().shutdown()
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
      **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
      message, timeout)
  DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.68 was 
not provided by any .service files"

  
  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...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1020572/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to