jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i have just ran the usb verison of ubuntu 11.10
and i was updating the files.
it ran then did a restart then this error came up.
i will say that i have not installed the Ubuntu program onto the laptop as of yet.
the hard drive has died and i was just running Ubuntu because it work off the usb.
never played with it before.
but when i get the new hard drive i will be installing it over the Windows Vista crap
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu10
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CasperVersion: 1.287.1
Date: Sat Feb 18 14:59:36 2012
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Acer Aspire 5536
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: noprompt cdrom-detect/
PythonArgs: ['/usr/
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: 02/27/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.03
dmi.board.name: JV50PU
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 5536
dmi.product.
dmi.sys.vendor: Acer
Thank you for taking the time to report this crash and helping to make this software 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.