Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #493780 reported by Vadim Ipatov on 2009-12-07

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

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

Architecture: i386
Date: Tue Dec 8 00:29: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.2)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
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=ru console-setup/layoutcode?=ru
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=ru_RU.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:3018): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:3018): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3079): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3105): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(gnome-panel:3074): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed
dmi.bios.date: 09/17/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1011.004
dmi.board.name: P4S800D
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1011.004:bd09/17/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnP4S800D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Tags:

Revision history for this message

Vadim Ipatov (euphoria-vi) wrote on 2009-12-07:

BootDmesg.txt Edit (33.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (757 bytes, text/plain; charset="utf-8")
Devices.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (553 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (477 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (88.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (188.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-12-08: 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.