Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #514665 reported by brahmaji_m on 2010-01-30

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 downloaded the ubuntu 9.10 iso and burnt it onto a cd. I tried to install it and in the wizard, while setting time zone the installation threw up this error and it gave me option to proceed anyway. Again the installation threw up another error in the next screen while selecting a keyboard layout.

ProblemType: Crash
.var.log.jockey.log: 2010-01-30 10:22:04,729 DEBUG: _check_polkit_privilege: sender :1.133 on connection <dbus._dbus.SystemBus (system) at 0xa5491ac> pid 3384 is not authorized for com.ubuntu.devicedriver.info: dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: i386
Date: Sat Jan 30 10:22:04 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
Bus 003 Device 002: ID 045e:0084 Microsoft Corp. Basic Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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 --
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:3231): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:3231): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3297): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(gnome-panel:3265): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -4 and height 24
dmi.bios.date: 11/08/2005
dmi.bios.vendor: Award BIOS for Intel
dmi.bios.version: GC11010N.86A.0303.2005.1108.2057
dmi.board.name: D101GGC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD35788-305
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardBIOSforIntel:bvrGC11010N.86A.0303.2005.1108.2057:bd11/08/2005:svn:pn:pvr:rvnIntelCorporation:rnD101GGC:rvrAAD35788-305:cvn:ct3:cvr:

Tags:

Revision history for this message

brahmaji_m (brahmaji007) wrote on 2010-01-30:

BootDmesg.txt Edit (60.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (33.3 KiB, text/plain; charset="utf-8")
Devices.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (534 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1004 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (96.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (197.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-01-30: 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.