Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #485958 reported by Bernard Decock on 2009-11-20

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 running livecd ubuntu

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

Architecture: i386
Date: Fri Nov 20 17:26:15 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: VIA Technologies, Inc. VT8363
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=nl console-setup/layoutcode?=us console-setup/variantcode?=intl
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=nl_NL.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:2931): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:2931): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:3006): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:3029): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(gdu-notification-daemon:3011): GduNotification-WARNING **: No notification area. Notification bubbles will not be displayed.
dmi.bios.date: 03/19/2002
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 8363/A-686A
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/19/2002:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363/A-686A:rvr:cvn:ct3:cvr:
dmi.product.name: VT8363
dmi.sys.vendor: VIA Technologies, Inc.

Tags:

Revision history for this message

Bernard Decock (decockbernard) wrote on 2009-11-20:

BootDmesg.txt Edit (32.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (16.6 KiB, text/plain; charset="utf-8")
Devices.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (5.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (437 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (443 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (75.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (167.8 KiB, text/plain; charset="utf-8")

Revision history for this message

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