Having another process locking the dpkg status database makes jockey crash instead of letting the user know the problem [apport: jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have tried to install the driver for a Toshiba printer (Manufacturer-
Instead of getting an informative message, jockey-backend crashed.
Steps to reproduce (on a system with hardware managed by jockey):
1. start a package manager with root privilege (aptitude, synaptic)
2. start jockey-gtk
3. try to activate/deactivate any driver listed.
4. crash
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu3 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelMo
Architecture: i386
Date: Tue Aug 30 17:39:48 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
MachineType: Gigabyte Technology Co., Ltd. P35-DS4
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 (2)
Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (2 days ago)
UserGroups:
dmi.bios.date: 05/11/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: P35-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P35-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
tags: | removed: need-duplicate-check |
summary: |
- jockey-backend crashed with SystemError: E:Sub-process /usr/bin/dpkg - returned an error code (2) + Having another process locking the dpkg status database makes jockey + crash instead of letting the user know the problem [apport: jockey- + backend crashed with SystemError: E:Sub-process /usr/bin/dpkg returned + an error code (2)] |
description: | updated |