jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)

[candyman]

unknown

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu10
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 8 17:45:23 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=b04f61a6-add3-4ccf-8523-74af5a53531e ro quiet splash vt.handoff=7
PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log']
SourcePackage: jockey
Title: jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/10/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 143F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 67.16
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd06/10/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D100000243210000020000:rvnHewlett-Packard:rn143F:rvr67.16:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 049D100000243210000020000
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 #850005, 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.