jockey-gtk crashed with DBusException in call_blocking()

Bug #509856 reported by Waldgeist_dI on 2010-01-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)

Bug Description

I was merely starting the Alpha2 of Lucid to fire up the live session. That's where the bug cropped up. I was asked to submit it. Anything else I can do?

uname -a
Linux ubuntu 2.6.32-10-generic #14-Ubuntu SMP Thu Jan 7 17:38:40 UTC 2010 i686 GNU/Linux


ProblemType: Crash
.var.log.jockey.log: 2010-01-19 21:35:53,508 DEBUG: _check_polkit_privilege: sender :1.60 on connection <dbus._dbus.SystemBus (system) at 0x86c914c> pid 3146 is not authorized for dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: i386
 [ 191.621951] lp: driver loaded but no devices found
 [ 191.866730] ppdev: user-space parallel port driver
 [ 267.660020] Clocksource tsc unstable (delta = -271496161 ns)
Date: Tue Jan 19 21:35:53 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: jockey-gtk 0.5.5-0ubuntu4
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcVersionSignature: Ubuntu 2.6.32-10.14-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-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare 06/12/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: 00000000 939SLI32-eSATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd06/12/2006:svn:pn939SLI32-eSATA2:pvr1.00:rvn:rn939SLI32-eSATA2:rvr1.00: 939SLI32-eSATA2
dmi.product.version: 1.00

Waldgeist_dI (noway) 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