jockey-gtk crashed with DBusException in call_blocking()

Bug #494720 reported by David Balažic on 2009-12-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)

Bug Description

I was reporting bug 494719 and at the end a dialog appeared that said jockey stopped responding or something (I'm sure the details are in the attached docs)

ProblemType: Crash

Architecture: amd64
Date: Wed Dec 9 20:41:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Hewlett-Packard HP Compaq nw8440 (RH415EA#ABB)
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
 Socket 0:
   no product info available
 Socket 0:
   no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper quiet splash --
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare 11/23/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YVD Ver. F.15 30A3
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 40.19
dmi.chassis.asset.tag: CNU6501JVS
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YVDVer.F.15:bd11/23/2007:svnHewlett-Packard:pnHPCompaqnw8440(RH415EA#ABB):pvrF.15:rvnHewlett-Packard:rn30A3:rvrKBCVersion40.19:cvnHewlett-Packard:ct10:cvr: HP Compaq nw8440 (RH415EA#ABB)
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard

David Balažic (xerces8) wrote :

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 #403955, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers