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
Updated the system which went ok. Then did a refresh and new updates appeared. When tried to update them, this crash notification appeared. Update manager did not close and after a while refreshed itself and there were no new updates. This is a Ubuntu 11.04 system so a beta still.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.146.3
ProcVersionSign
Uname: Linux 2.6.31-11-generic i686
NonfreeKernelMo
Architecture: i386
Date: Sun Mar 13 00:31:21 2011
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/
ProcEnviron:
LANGUAGE=fi_FI:en
PATH=(custom, user)
LANG=fi_FI.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: update-manager
Title: update-manager crashed with DBusException in _run(): org.freedesktop
UpgradeStatus: Upgraded to natty on 2011-03-05 (7 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy lpadmin netdev plugdev powerdev sambashare scanner tape video
| Esko Kauppinen (esko-kauppinen) 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.