Exception comes during installation lucid lynx dayly 20091224
ProblemType: Crash
.var.log.jockey.log: 2009-12-24 19:39:21,212 DEBUG: _check_polkit_privilege: sender :1.45 on connection <dbus._dbus.SystemBus (system) at 0x919d11c> pid 3745 is not authorized for com.ubuntu.devicedriver.info: dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: i386
Date: Thu Dec 24 19:39:21 2009
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091224)
MachineType: IBM 1834S3G
Package: jockey-gtk 0.5.5-0ubuntu4
PackageArchitecture: all
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xhostname.seed boot=casper apparmor=0 initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-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-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/08/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1WET90WW (2.10 )
dmi.board.name: 1834S3G
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn1834S3G:pvrThinkPadR50e:rvnIBM:rn1834S3G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 1834S3G
dmi.product.version: ThinkPad R50e
dmi.sys.vendor: IBM
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.