Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #463808 reported by tinix84 on 2009-10-29

This bug report is a duplicate of: Bug #403955: jockey crashed during installation of ubuntu, apparently no effect on the installation, which continued normally. Edit Remove

This bug affects 1 person

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

Bug Description

i don-t know

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

Architecture: i386
Date: Thu Oct 29 21:07:21 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: TOSHIBA Satellite U400
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=en_US.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:3418): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:3418): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3515): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3535): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 08/25/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V3.20
dmi.board.name: Satellite U400
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV3.20:bd08/25/2008:svnTOSHIBA:pnSatelliteU400:pvrPSU40E-00T00XIT:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U400
dmi.product.version: PSU40E-00T00XIT
dmi.sys.vendor: TOSHIBA

Tags:

Revision history for this message

tinix84 (tinix84) wrote on 2009-10-29:

BootDmesg.txt Edit (53.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (820 bytes, text/plain; charset="utf-8")
Devices.txt Edit (3.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (646 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (107.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (221.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-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 #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.