software-center crashed with DBusException in call_blocking()

[Wouter Stomp]

Binary package hint: software-center

Software center seems to become unstable when the connection to apt-daemon is lost. First an error messages popped up telling me the connection was lost. The tab on the left showed one programming still installing but when going to that tab it was empty. Then after restarting softwware-center it still showed one programming being installed, and when going to that tab it showed one program without a name stuck at 0%. Then the program crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 12:59:27 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: fglrx
Package: software-center 0.4.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2041): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2041): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2281): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2248): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[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 #440597, 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.