Ubuntu
debconf package

package debconf 1.5.27ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #441888 reported by WiFi Ed on 2009-10-04

This bug report is a duplicate of: Bug #442941: debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Edit Remove

150

This bug affects 34 people

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

Bug Description

Binary package hint: debconf

karmic koala beta x64

upgrade of a clean beta installation fails after downloading the upgrades.

ProblemType: Package
Architecture: amd64
Date: Sat Oct 3 19:14:51 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 128
Package: debconf 1.5.27ubuntu2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: debconf
Title: package debconf 1.5.27ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Uname: Linux 2.6.31-11-generic x86_64

Tags:

Revision history for this message

WiFi Ed (moran-ed) wrote on 2009-10-04:

AptOrdering.txt Edit (8.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (481 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (52.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (9.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Erwin Michel (erwin-swisscc) wrote on 2009-10-15:

The upgrade did not go well.

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-01-20:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 442941, so it 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.