Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking()

Bug #489864 reported by Alain SAURAT on 2009-11-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 had just create an USB stick with Lucid Lynx alpha and try it on my EeePC 701.
The boot sequence was good, but after one minute of inactivity, this bug appears....

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

Architecture: i386
Date: Sun Nov 29 08:37:10 2009
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091128)
MachineType: ASUSTeK Computer INC. 701
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=fr console-setup/layoutcode?=fr console-setup/variantcode?=oss
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1302
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/11/2009:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Tags:

Revision history for this message

Alain SAURAT (maisondouf) wrote on 2009-11-29:

BootDmesg.txt Edit (37.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Devices.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (452 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (539 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (991 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (88.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (194.0 KiB, text/plain; charset="utf-8")

Revision history for this message

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