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

Bug #858653 reported by Sem Brignoli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
New
Undecided
Unassigned

Bug Description

While installing Nvidia Drivers

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sat Sep 24 22:55:41 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.7
MachineType: BIOSTAR Group N68SB-M2S
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-11-generic root=UUID=9251cae7-5f2e-435f-a8d0-e5f178107995 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 (2)
Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/24/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: N68SB-M2S
dmi.board.vendor: BIOSTAR Group
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: N68SB-M2S
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/24/2010:svnBIOSTARGroup:pnN68SB-M2S:pvr:rvnBIOSTARGroup:rnN68SB-M2S:rvr:cvnBIOSTARGroup:ct3:cvrN68SB-M2S:
dmi.product.name: N68SB-M2S
dmi.sys.vendor: BIOSTAR Group

Revision history for this message
Sem Brignoli (hamacaweb) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.