jockey-gtk crashed with DBusException in call_blocking()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I had booted the Karmic amd64 livecd; I had selected F6 to add options to the command line, removed "quiet" and "splash" and added "single". With a Jaunty livecd, this would allow me to drop into a root shell, change my hostname (my network at work requires my MAC address to be associated with a particular name) and then resume normal boot. I separately reported the problem that in Karmic (beta and release candidate) the resuming normal boot didn't bring up the gui. I typed startx to attempt to get x going, and it mostly did, but I got notifications of two programs' crashing, including jockey. I selected the "report" option on each popup, but appport told me it couldn't report the other program's problem because it couldn't retrieve the message. (Perhaps I should only have attempted to report one crash at a time? I have little experience with appport.) Looking in /var/crash I see that the crash file for the other program was named _usr_lib_
I noticed as the boot message scrolled by that some initialization scripts had already set the hostname and regenerated some SSL certificates and I also got popup dialogs about not being authorized, all of which may play into this problem.
The upshot is that the Karmic livecd is complete useless for me at work; the Jaunty livecd was completely useful. Blecch.
ProblemType: Crash
.var.log.
Architecture: amd64
CurrentDmesg:
[ 256.119354] [drm] Setting GART location based on new memory map
[ 256.122439] [drm] Loading R300 Microcode
[ 256.122472] [drm] Num pipes: 1
[ 256.122484] [drm] writeback test succeeded in 1 usecs
Date: Sat Oct 31 12:55:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 5986:0100 Acer, Inc Orbicam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5100
Package: jockey-gtk 0.5.5-0ubuntu2
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:
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 x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(nautilus:3438): Eel-CRITICAL **: eel_preferences
(polkit-
(gnome-
dmi.bios.date: 03/21/2007
dmi.bios.vendor: Acer
dmi.bios.version: V2.83
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.