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

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

Bug Description

jockey

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.2-0ubuntu8
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Thu Jul 7 08:06:02 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110618)
InterpreterPath: /usr/bin/python2.7
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-3-generic root=UUID=13c0350f-113a-4bba-a299-98238e77d2bd 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-07-06 (0 days ago)
UserGroups:

dmi.bios.date: 09/14/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZD Ver. F.12
dmi.board.name: 30E9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 95.1D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.12:bd09/14/2009:svnHewlett-Packard:pn:pvrF.12:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
abinstudy (abinstudy) 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 #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.

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.