jockey-gtk crashed with DBusException in call_blocking()

Bug #543283 reported by Fredrik Folkeryd
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

crashed noticed when waking from "Sleep"

ProblemType: Crash
Architecture: i386
Date: Sun Mar 21 10:48:19 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100223.2)
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Latitude D505
Package: jockey-gtk 0.5.8-0ubuntu1
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=36eafaca-60eb-4707-acfe-7851d27635f7 ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk -c
ProcEnviron:
 LANG=sv_SE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/bin/jockey-gtk', '-c']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/26/2004
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0H2049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/26/2004:svnDellInc.:pnLatitudeD505:pvr:rvnDellInc.:rn0H2049:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D505
dmi.sys.vendor: Dell Inc.

Revision history for this message
Fredrik Folkeryd (fredrik.folkeryd) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 657829, so it 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.

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.