jockey-gtk crashed with DBusException in call_blocking()

Bug #517217 reported by Michael Casadevall on 2010-02-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Undecided
Unassigned

Bug Description

Crash on armel at boot time. No specific actions taken.

ProblemType: Crash
.var.log.jockey.log: 2010-02-04 19:37:02,703 DEBUG: _check_polkit_privilege: sender :1.54 on connection <dbus._dbus.SystemBus (system) at 0x4ddf30> pid 2707 is not authorized for com.ubuntu.devicedriver.info: dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: armel
CurrentDmesg: [ 101.439965] eth0: no IPv6 routers present
Date: Thu Feb 4 19:37:03 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha armel+dove (20100202.2)
Lspci:

NonfreeKernelModules: squashfs aufs nls_iso8859_1 nls_cp437 usbhid sg
Package: jockey-gtk 0.5.5-0ubuntu4
PackageArchitecture: all
ProcCmdLine: console=ttyS0,115200 file=/cdrom/preseed/hostname.seed -- boot=casper
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-200.6mvldoveapw1-dove
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-200-dove armv7l
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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