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

[Domenico LANDO]

No details

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Oct 5 22:33:53 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HPE-330it
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=dff672eb-2d53-4de5-bba2-487a3052931a 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-10-05 (0 days ago)
UserGroups:

dmi.bios.date: 07/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.12
dmi.board.name: 2A9C
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: CZC0236NCB
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.12:bd07/12/2010:svnHewlett-Packard:pnHPE-330it:pvrxxx0204GRxxxxxxxx0:rvnMSI:rn2A9C:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HPE-330it
dmi.product.version: xxx0204GRxxxxxxxx0
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.