jockey-gtk crashed with DBusException in call_blocking()

Bug #471219 reported by shooroop on 2009-11-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)

Bug Description

Binary package hint: jockey-gtk

1) Description: Ubuntu 9.10
Release: 9.10
2) jockey-gtk 0.5.5-0ubuntu2
3) it crashed when I logged in LiveCD mode from USB-stick

ProblemType: Crash
.var.log.jockey.log: 2009-11-02 15:59:38,534 DEBUG: _check_polkit_privilege: sender :1.59 on connection <dbus._dbus.SystemBus (system) at 0x91a41ac> pid 4556 is not authorized for dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: i386
Date: Mon Nov 2 15:59:38 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: Acer Aspire 5315
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=ru console-setup/layoutcode?=ru
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
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 08/09/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.14
dmi.board.asset.tag: Base Board Asset Tag Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.14
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.14
dmi.modalias: dmi:bvnAcer:bvrV1.14:bd08/09/2007:svnAcer:pnAspire5315:pvrV1.14:rvnAcer:rnAcadia:rvrV1.14:cvnAcer:ct1:cvrV1.14: Aspire 5315
dmi.product.version: V1.14
dmi.sys.vendor: Acer

shooroop (shooroop) 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