Ubuntu
debconf package

package debconf 1.5.41ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Bug #957026 reported by ronrgrs on 2012-03-16

This bug report is a duplicate of: Bug #1058884: Race condition in py_compile corrupts pyc files. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	debconf (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

tried running apt-get -f install. it did not help

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: debconf 1.5.41ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
AptOrdering:
debconf: Install
debconf: Configure
Architecture: i386
Date: Fri Mar 16 10:38:14 2012
ErrorMessage: subprocess new pre-removal script returned error exit status 1
PackageArchitecture: all
SourcePackage: debconf
Title: package debconf 1.5.41ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

ronrgrs (rr-59-roadrunner) wrote on 2012-03-16:

Dependencies.txt Edit (438 bytes, text/plain; charset="utf-8")
Df.txt Edit (329 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.6 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (72.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (655 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-10-19:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in debconf (Ubuntu):
status:	New → Confirmed

Revision history for this message

Peter Velosy (petervelosy) wrote on 2012-10-19:

This occured to me when upgrading from 12.04 to 12.10 using update-manager, along with the same error for python3, libpam-modules and lsb. The upgrade terminated with a message like "Process aborted, too many errors", then the Restart button was shown, but I was presented with an unusable OS that boots into a black screen, and where repair mode didn't work either (it simply did nothing after running fsck). I had to reinstall everything from scratch.