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

[James Kemp]

running on live USB to check if the wireless issue encountered in 11.04 has been fixed. But apparently not.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CasperVersion: 1.284
Date: Tue Oct 4 20:19:00 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
MachineType: Acer Aspire one
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/04/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.09
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire one
dmi.board.vendor: Acer
dmi.board.version: V1.09
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias: dmi:bvnAcer:bvrV1.09:bd06/04/2009:svnAcer:pnAspireone:pvrV1.09:rvnAcer:rnAspireone:rvrV1.09:cvnAcer:ct1:cvrV1.09:
dmi.product.name: Aspire one
dmi.product.version: V1.09
dmi.sys.vendor: Acer

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