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

[Prasad Murthy]

Messagebox pops up frequently saying"System problems detected"

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Sep 3 10:16:27 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.7
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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-9-generic root=/dev/sda3 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-26 (7 days ago)
UserGroups:

dmi.bios.date: 02/22/2006
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EV91510A.86A.0482.2006.0222.2350
dmi.board.name: D915GAV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC64138-403
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrEV91510A.86A.0482.2006.0222.2350:bd02/22/2006:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64138-403:cvn:ct2:cvr:

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