update-manager crashed with DBusException in _run()

[David R. Hedges]

Binary package hint: update-manager

The update notifier informed me that my i386 Maverick system had updates available (as was to be expected after a weekend for a pre-release version). I opened update manager, clicked "check" to make sure I was grabbing the latest packages, and then clicked install updates. I entered my password in the "administrative task" dialog that appeared, and not very long later, saw the crash reported. Even while the crash report window was up, the system was under moderate load, and I investigated and saw that update-manager was still running, and apt/dpkg were also running, and applying updates.

---
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
---
#run after the background apt/dpkg processes had finished, so it's possible this has been updated since the crash occurred.
$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.142.15
  Candidate: 1:0.142.15
  Version table:
 *** 1:0.142.15 0
        700 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.15
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Sep 27 17:03:58 2010
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with DBusException in _run()
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner 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.