jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions() while starting the ubuntu installation wizard on a live CD environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1)
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
2)
ubuntu@ubuntu:~$ apt-cache policy jockey
N: Unable to locate package jockey
ubuntu@ubuntu:~$ apt-cache policy jockey-gtk
jockey-gtk:
Installed: 0.5.10-0ubuntu5
Candidate: 0.5.10-0ubuntu5
Version table:
*** 0.5.10-0ubuntu5 0
500 http://
100 /var/lib/
3)
Don't know, was installing ubuntu and
4)
Apport said "jockey crashed"
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: jockey-gtk 0.5.10-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sun Jan 9 13:59:02 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO 6474AV4
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: file=/cdrom/
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with BackendCrashError in convert_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/09/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET56WW (2.02 )
dmi.board.name: 6474AV4
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 6474AV4
dmi.product.
dmi.sys.vendor: LENOVO
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 #645922, 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.