jockey-gtk crashed with KeyError in __getitem__(): 'package'

Bug #838622 reported by griffinpeterson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Jockey crashed after the automatic check in the background at system start. When I start jockey manually it doesn't crash, but
won't show any proprietary drivers, even though I have a nvidia card and a b43 wlan module. Their drivers I installed manually and I know that at least the b43 driver is working (not sure about nvidia but there is a nvidia splash at system start), but they are not shown in the jockey UI.
Kind regards

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Aug 29 17:12:52 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse
MachineType: ASUSTeK Computer INC. A6M
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=9a0fc9cc-2382-46de-a135-3c6f51b7a7da ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk', '--no-dbus']
SourcePackage: jockey
Title: jockey-gtk crashed with KeyError in __getitem__(): 'package'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/23/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080012
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A6M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd10/23/2006:svnASUSTeKComputerINC.:pnA6M:pvr1.0:rvnASUSTeKComputerINC.:rnA6M:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: A6M
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
griffinpeterson (griffinpeterson) 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 #836714, 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.