jockey-gtk crashed with DBusException in call_blocking()

Bug #440907 reported by Łukasz Czerwiński
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu Karmic 9.10

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

Architecture: amd64
Date: Fri Oct 2 22:55:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5505
Package: jockey-gtk 0.5.4-0ubuntu1
PackageArchitecture: all
ProcCmdLine: root=UUID=4e15f3c2-1af3-4894-91d4-41f3fd494b85 ro quiet splash vga=788
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check-composite
ProcCwd: /home/milimetr
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check-composite']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare video
dmi.bios.date: 12/06/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-A0Y
dmi.board.name: ESPRIMO Mobile V5505
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2040
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Y:bd12/06/2007:svnFUJITSUSIEMENS:pnESPRIMOMobileV5505:pvr20:rvnFUJITSUSIEMENS:rnESPRIMOMobileV5505:rvrNotApplicable:cvnFUJITSUSIEMENS:ct10:cvrA2040:
dmi.product.name: ESPRIMO Mobile V5505
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Łukasz Czerwiński (milimetr88) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #400638, 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.