jockey-gtk crashed with DBusException in call_blocking()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Jockey crashed upon booting the live CD, however installation appeared unaffected.
Similar to https:/
ProblemType: Crash
.var.log.
Architecture: amd64
CurrentDmesg:
[ 151.973365] lp: driver loaded but no devices found
[ 152.501523] ppdev: user-space parallel port driver
[ 155.521843] cfg80211: Found new beacon on frequency: 5180 MHz (Ch 36) on phy0
[ 156.410024] cfg80211: Found new beacon on frequency: 5805 MHz (Ch 161) on phy0
Date: Thu Jan 14 23:37:24 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
MachineType: Hewlett-Packard HP Pavilion dv9500 Notebook PC
Package: jockey-gtk 0.5.5-0ubuntu4
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: jockey
Tags: lucid
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/24/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.52
dmi.board.name: 30CB
dmi.board.vendor: Quanta
dmi.board.version: 79.29
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv9500 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.