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.

[Rachel Greenham]

Binary package hint: update-manager

system has too little mmory and very slow ssd drive for system and swap (1st gen acer aspire one); any 'disk' access causes io lock of entire system; probably accounts for this timout.

ought to give up on it really, unless you still want to target such a machine... ?

nb: as i type,the upgrade itself is still progressing in background, visible through tail -f /var/log/apt/term.log

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.146.5
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Thu Mar 24 18:57:11 2011
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: 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.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

[Apport retracing service (apport)]

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.