Ubuntu
jockey package

jockey crash just after booting live cd

Bug #492932 reported by Problem on 2009-12-05

This bug report is a duplicate of: Bug #275659: jockey-gtk crashed with DBusException in call_blocking() ("Activation of com.ubuntu.DeviceDriver timed out"). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	jockey (Ubuntu)	New	Undecided	Unassigned

Bug Description

After booting karmic live cd I got a window saying that jockey (is it jockey-gtk? at least this is the gnome flavour of ubuntu) had crashed and offering to send a bug report. I had booted before on the same system without this error.

ProblemType: Crash
.var.log.jockey.log:

Architecture: i386
Date: Sat Dec 5 20:22:44 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)
MachineType: HP Pavilion 061 EV919AA-ABE m7430.es
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=es console-setup/layoutcode?=es
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
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 i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-settings-daemon:3745): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:3745): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3798): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3830): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 03/24/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.48
dmi.board.name: AMETHYST-M
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.48:bd03/24/2006:svnHPPavilion061:pnEV919AA-ABEm7430.es:pvr0ny0114RE101AMETM00:rvnMSI:rnAMETHYST-M:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: EV919AA-ABE m7430.es
dmi.product.version: 0ny0114RE101AMETM00
dmi.sys.vendor: HP Pavilion 061

Tags:

Revision history for this message

Problem (notyourbusiness555555) wrote on 2009-12-05:

BootDmesg.txt Edit (40.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Devices.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (415 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (519 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (122.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (227.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-12-05: This bug is a duplicate

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.