jockey-gtk 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 opened up Jockey from Control Center and it would not close then it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Fri Jul 29 15:20:41 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite L35
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: Upgraded to oneiric on 2011-07-26 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/12/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.30
dmi.board.name: Satellite L35
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite L35
dmi.product.
dmi.sys.vendor: TOSHIBA
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 #657829, 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.