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
first reboot into Gnome Classic after upgrading from 11.04 to 11.10
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu7
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Jan 4 12:19:02 2012
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
MachineType: ASUSTeK Computer INC. V-P8H67E
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: Upgraded to oneiric on 2012-01-04 (0 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse pulse-access sambashare video
dmi.bios.date: 03/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.
dmi.board.name: V-P8H67E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: V-P8H67E
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
Thank you for taking the time to report this crash and helping to make this software 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.