jockey-gtk crashed with DBusException in call_blocking() - Crashed while loading live cd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
loading up the 9.10 live cd. Crashed on loading.
ProblemType: Crash
.var.log.
Architecture: i386
Date: Tue Dec 15 02:18:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
Bus 001 Device 002: ID 0411:0089 MelCo., Inc. Buffalo RUF-C/U2 Flash Drive
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 264786G
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(nautilus:2800): Eel-CRITICAL **: eel_preferences
(polkit-
dmi.bios.date: 12/21/1999
dmi.bios.vendor: IBM
dmi.bios.version: IYET59WW (1.20 )
dmi.board.name: 264786G
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 264786G
dmi.product.
dmi.sys.vendor: IBM
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 #275659, 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.