backend_helper.py crashed with RuntimeError in add_signal_receiver(): To make asynchronous calls, receive signals or export objects, D-Bus connections must be attached to a main loop by passing mainloop=... to the constructor or calling dbus.set_default_main_loop(...)

[Chris Peach]

This occurred on the first run of today's daily-live desktop image after starting the desktop before I did anything.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-notifier-common 0.118.1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic-pae 3.2.1
Uname: Linux 3.2.0-11-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CasperVersion: 1.301
Date: Sat Jan 28 10:00:43 2012
DuplicateOf: https://bugs.launchpad.net/bugs/875970
ExecutablePath: /usr/lib/update-notifier/backend_helper.py
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120128)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/backend_helper.py add_cdrom /cdrom
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/update-notifier/backend_helper.py', 'add_cdrom', '/cdrom']
SourcePackage: update-notifier
Title: backend_helper.py crashed with RuntimeError in add_signal_receiver(): To make asynchronous calls, receive signals or export objects, D-Bus connections must be attached to a main loop by passing mainloop=... to the constructor or calling dbus.set_default_main_loop(...)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #875970, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.