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

[Grifter]

I installed Jockey because it appeared that I didn't have restricted drivers installed, and when I looked for it, I found Jockey. Now it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Sep 28 11:32:29 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Alienware M11x
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=8ab94188-1825-4e40-bb42-91baa320a057 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 (1)
Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (0 days ago)
UserGroups:

dmi.bios.date: 05/20/2010
dmi.bios.vendor: Alienware
dmi.bios.version: A04
dmi.board.name: 08JG36
dmi.board.vendor: Alienware
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A04
dmi.modalias: dmi:bvnAlienware:bvrA04:bd05/20/2010:svnAlienware:pnM11x:pvrA04:rvnAlienware:rn08JG36:rvrA04:cvnAlienware:ct8:cvrA04:
dmi.product.name: M11x
dmi.product.version: A04
dmi.sys.vendor: Alienware

[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.