update-manager crashed with DBusException in _run(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: update-manager
Happens intermittently, regardless of the age of the install (a fresh installation can produce the same error within a few updates). Verified that the network connect on this particular machine is stable, as is the internet connection. Updates still seem to proceed normally in spite of this error.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.146.5
ProcVersionSign
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
Date: Wed Mar 16 13:23:55 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110315)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: update-manager
Title: update-manager crashed with DBusException in _run(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| QPrime (mwells) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #626798, 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.