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
Description: Ubuntu Natty (development branch)
Release: 11.04
update-manager:
Installed: 1:0.146.5
Candidate: 1:0.146.5
Version table:
*** 1:0.146.5 0
500 http://
100 /var/lib/
All things considered, not surprising. Will use workaround by running apt-get update from a terminal
One note is that the authorization pop-up should position the cursor to received the password. Bad Programmer! Bad! Bad!
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.146.5
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Mar 30 16:56:02 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, user)
LANG=en_CA.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-28 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
On checking with the apt-get upgrade tool, I found that, even though there was a failure in update-manager, the updates had been done. It appears to ahve been some kind of communication failure between processes.