software-center crashed with DBusException in call_blocking(): 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 | |
|---|---|---|---|---|---|
| software-center (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Description: Ubuntu oneiric (development branch)
Release: 11.10
software-center:
Installed: 4.1.23.3
Candidate: 4.1.23.3
Version table:
*** 4.1.23.3 0
500 http://
100 /var/lib/
Out of the blue. I wasn't running this program, so I guess it was some daemon that crashed. There are too many daemons in this system.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-center 4.1.23.3
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 20 19:53:59 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
PythonArgs: ['/usr/
SourcePackage: software-center
Title: software-center crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| John Winterton (jwinterton) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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 #705215, 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.