Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #495720 reported by Drakeskywing on 2009-12-12

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

During the install i noticed a series of random packages started crashing from jockey, to empathy and something called butterfly. This is the second time i've tried reinstalling 9.10 because the first time after what it said was a successful install the screen flashed continuously and was only responsive when the screen was at normal contrast.

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

Architecture: i386
Date: Sat Dec 12 11:38:17 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: Dell Inc. Inspiron 1720
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:3516): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:3516): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3572): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3597): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 07/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0UK437
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK437:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1720
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Drakeskywing (drakeskywing) wrote on 2009-12-12:

BootDmesg.txt Edit (47.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Devices.txt Edit (3.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (712 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (117.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (221.9 KiB, text/plain; charset="utf-8")

Revision history for this message

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