jockey-kde 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 | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i canceled the install of a driver nvidia (current-updates) and when the window became active again all the items in the list were disabled (greyed out). when i pushed the close button it crashed and each time afterward it faied to launch
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-kde 0.9.4-0ubuntu5
ProcVersionSign
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Tue Sep 6 22:11:17 2011
ExecutablePath: /usr/bin/jockey-kde
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
InterpreterPath: /usr/bin/python2.7
MachineType: Apple Inc. MacBookPro6,2
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-kde crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/26/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.
dmi.board.
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro6,2
dmi.product.
dmi.sys.vendor: Apple Inc.
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 #831803, 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.