jockey-gtk crashed with DBusException in call_blocking()

[Steve Beattie]

This occurred after a fresh installation from the alt-i386 iso from 20100106.

ProblemType: Crash
Architecture: i386
Date: Wed Jan 6 11:30:45 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
InterpreterPath: /usr/bin/python2.6
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7418
Package: jockey-gtk 0.5.5-0ubuntu4
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-9-generic root=UUID=64d2c0b9-c806-493c-afb4-267d6020a754 ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Tags: lucid
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/21/2008
dmi.bios.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.bios.version: 1.50
dmi.board.name: MS-7418
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 100
dmi.chassis.type: 4
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.modalias: dmi:bvnMICRO-STARINTERNATIONALCO.,LTD:bvr1.50:bd10/21/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7418:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7418:rvr100:cvnMICRO-STARINTERNATIONALCO.,LTD:ct4:cvr:
dmi.product.name: MS-7418
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[Apport retracing service (apport)]

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.