jockey-gtk crashed with DBusException in call_blocking()

Bug #462313 reported by Tobin Davis on 2009-10-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Undecided
Unassigned

Bug Description

Starting the installer on 20091027.2 Karmic-desktop-armel+dove.img. Nothing special otherwise.

ProblemType: Crash
.var.log.jockey.log: 2009-10-28 00:49:24,582 DEBUG: _check_polkit_privilege: sender :1.58 on connection <dbus._dbus.SystemBus (system) at 0x537f00> pid 2994 is not authorized for com.ubuntu.devicedriver.info: dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: armel
CurrentDmesg: eth0: no IPv6 routers present
Date: Wed Oct 28 00:49:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release armel+dove (20091027.2)
Lspci:

Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: quiet splash 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.31-208.16-dove
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-208-dove armv7l
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2923): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2923): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2980): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2996): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Tobin Davis (gruemaster) 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