jockey-gtk crashed with DBusException in call_blocking()

Bug #469594 reported by gadeynebram on 2009-11-01
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Undecided
Unassigned

Bug Description

during installation of ubuntu 9.10

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

Architecture: amd64
Date: Sun Nov 1 23:02:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: FUJITSU SIEMENS AMILO Notebook Xa 3530
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity 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 x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/09/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V2.08
dmi.board.name: X17
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 2A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2040
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV2.08:bd01/09/2009:svnFUJITSUSIEMENS:pnAMILONotebookXa3530:pvr10600944869:rvnFUJITSUSIEMENS:rnX17:rvr2A:cvnFUJITSUSIEMENS:ct10:cvrA2040:
dmi.product.name: AMILO Notebook Xa 3530
dmi.product.version: 10600944869
dmi.sys.vendor: FUJITSU SIEMENS

gadeynebram (gadeynebram-gmail) wrote :

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers