jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()

[Peter Subda]

The only difference from the previous bug report is the machine type. The other was Dell, mine is Acer Aspire AM3910-E2512

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 x86_64
Architecture: amd64
CurrentDmesg:
 [ 61.053570] eth0: no IPv6 routers present
 [ 206.580729] JFS: nTxBlock = 8192, nTxLock = 65536
 [ 206.716567] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
 [ 206.717274] SGI XFS Quota Management subsystem
Date: Thu Oct 14 06:44:40 2010
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Acer Aspire M3910
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: 05/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Aspire M3910
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnAcer:pnAspireM3910:pvr:rvnAcer:rnAspireM3910:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire M3910
dmi.sys.vendor: Acer

[Apport retracing service (apport)]

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.