Ubuntu
software-center package

Authentification took too long, crash after pressing cancel.

Bug #443060 reported by joezuyuz on 2009-10-05

This bug report is a duplicate of: Bug #440597: software-center crashed with DBusException in call_blocking(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	software-center (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: software-center

Tried to download blender, but authentication timed out, and the screen grayed, so I clicked cancel. The software center was then frozen and needed to be closed. Upon restart, I couldn't download blender anymore, since software center says it's already installed.

ProblemType: Crash
Architecture: amd64
Date: Mon Oct 5 08:21:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: software-center 0.4.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
LANG=en_US.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 x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

joezuyuz (joezuyus) wrote on 2009-10-05:

Traceback.txt Edit (790 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (676 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-05: This bug is a duplicate

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.