jockey-gtk crashed with DBusException in call_blocking() on Live USB Ubuntu 9.10 "Super OS"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is a default un-changed iso image of Ubuntu 9.10 "Super OS", running on USB Thumb-drive.
Acer Aspire 5100-5455
No proprietary divers in use & everything is working fine. When Iogged in, I received an error message to report this bug, so I did.
ProblemType: Crash
Architecture: i386
Date: Tue Mar 16 21:14:38 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer Aspire 5100
Package: jockey-gtk 0.5.5-0ubuntu3
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
PATH=(custom, no user)
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:4803): Eel-CRITICAL **: eel_preferences
(polkit-
dmi.bios.date: 08/22/2008
dmi.bios.vendor: Acer
dmi.bios.version: V3.13
dmi.board.name: Navarro
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5100
dmi.product.
dmi.sys.vendor: Acer
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.