jockey-gtk crashed with DBusException in call_blocking()

Bug #491970 reported by Benny Källström on 2009-12-03
This bug affects 2 people
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)

Bug Description

I was installing Ubuntu 10.4 daily build, and this message showed up.

ProblemType: Crash

Architecture: i386
Date: Thu Dec 3 18:06:16 2009
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091203)
MachineType: Hewlett-Packard HP Compaq 6830s
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=sv console-setup/layoutcode?=se
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcVersionSignature: Ubuntu 2.6.32-6.8-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Tags: lucid
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare 03/12/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZD Ver. F.0C 30E9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 95.1C
dmi.chassis.asset.tag: CNU9202RW6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: HP Compaq 6830s
dmi.product.version: F.0C
dmi.sys.vendor: Hewlett-Packard

Benny Källström (benny-k) wrote :
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 #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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers