jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()

Bug #662626 reported by craigsn@hotmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was installing this in VirtualBox 3.2.10 (new install), and on the initial install, there was a problem saying the installer crashed. The install did not complete, but took me to the live cd desktop. That is all I know about this error

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: jockey-gtk 0.5.10-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Oct 18 09:47:13 2010
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 002 Device 002: ID 80ee:0021
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
craigsn@hotmail.com (craigsn-hotmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.