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

[akand074]

Occurred immediately after login.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sun Sep 4 13:41:08 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP TouchSmart tx2 Notebook PC
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus -k 3.0.0-9-generic
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
 LANGUAGE=en_CA.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=fc29d9fc-e577-4bcf-b44d-558923181a60 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-text', '-C', '--no-dbus', '-k', '3.0.0-9-generic']
SourcePackage: jockey
Title: jockey-text crashed with KeyError in __getitem__(): 'package'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/25/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3045
dmi.board.vendor: Quanta
dmi.board.version: 16.14
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.21:bd08/25/2009:svnHewlett-Packard:pnHPTouchSmarttx2NotebookPC:pvrRev1:rvnQuanta:rn3045:rvr16.14:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP TouchSmart tx2 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

[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 #837730, 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.