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 do not know what is the aplication. System freeze and logout ( during smal playing console at ALT + CTRL + F1 ) after code:
sudo su -
apt-get update
apt-get upgrade
and installing flash-player and pressing ALT + TAB.
I subscribe bug #825587 in same time.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelMo
.var.log.
Architecture: amd64
Date: Wed Aug 17 21:11:44 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110816)
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 002 Device 002: ID 045e:0083 Microsoft Corp. Basic Optical Mouse
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
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/17/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: MS-7100
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
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.