jockey-gtk crashed with DBusException in call_blocking()

[Danilo]

Live session user

ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
ubuntu@ubuntu:~$ apt-cache policy jockey-gtk
jockey-gtk:
  Installato: 0.5.5-0ubuntu2
  Candidato: 0.5.5-0ubuntu2
  Tabella versione:
 *** 0.5.5-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

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

Architecture: i386
Date: Thu Nov 19 15:29:47 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: MICRO-STAR INTERNATIONAL CO., LTD MS-7181
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=it console-setup/layoutcode?=it
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=it_IT.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
dmi.bios.date: 01/20/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7181
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 2.0
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/20/2006:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7181:pvr2.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7181:rvr2.0:cvn:ct3:cvr:
dmi.product.name: MS-7181
dmi.product.version: 2.0
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.