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
i get this error when i type a wrong password, or wait too long (apparently) to type my password.
i i type my correct password right away, i don't get the error.
update process continues on the background.
regarding bug title:
" 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."
i suspect the remote application to be fine
i don't know about message security policy
the reply timeout could be the culprit
network is working fine
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.146.1
ProcVersionSign
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Tue Mar 8 17:02:20 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python2.7 /usr/bin/
ProcEnviron:
LANGUAGE=
LANG=nl_NL.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-03 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.