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

[Ixulescovici]

Junk

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Aug 19 13:27:59 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: FUJITSU SIEMENS G31T-M2
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-8-generic root=UUID=8f3f5aed-6568-41f1-8aed-66100a223ca5 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-08-19 (0 days ago)
UserGroups:

dmi.bios.date: 09/07/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.02
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31T-M2
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: V3.02
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.02:bd09/07/2007:svnFUJITSUSIEMENS:pnG31T-M2:pvrV3.02:rvnFUJITSUSIEMENS:rnG31T-M2:rvrV3.02:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: G31T-M2
dmi.product.version: V3.02
dmi.sys.vendor: FUJITSU SIEMENS

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