jockey-gtk crashed with DBusException in call_blocking() (DBusException: com.ubuntu.DeviceDriver.PermissionDeniedByPolicy: com.ubuntu.devicedriver.info)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This seemed to cause the X session to terminate suddenly -- in which case it would be considered serious.
However, I unintentionally mashed the keyboard just before or at the same time that this error happened, and it's possible that some key combination I hit caused the logout instead. Note that there was no dialog box confirming the logout as would usually be the case, but instead the session logged out abruptly.
ProblemType: Crash
Architecture: armel
Date: Tue Oct 27 13:06:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release armel+imx51 (20091027.1)
Lspci:
Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
Lsusb:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0dc6:3412 Precision Squared Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:2517 Standard Microsystems Corp.
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitec
ProcCmdLine: console=
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-105-imx51 armv7l
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(nautilus:3027): Eel-CRITICAL **: eel_preferences
(polkit-
(gnome-
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.