Ubuntu
debconf package

package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #566995 reported by Chipp on 2010-04-20

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

This bug affects 1 person

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

Bug Description

Binary package hint: postfix

In process of installing mail-notification from Ubuntu Software Center - process hangs at 88%.

Ubuntu 10.04, updated fully as of Apr 19th 9:06pm EST.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: postfix 2.7.0-1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Mon Apr 19 21:03:45 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
SourcePackage: postfix
Title: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Tags:

Revision history for this message

Chipp (sethhochberg) wrote on 2010-04-20:

AptOrdering.txt Edit (789 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (954 bytes, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (55.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (27.1 KiB, application/x-gzip)

Chuck Short (zulcss) on 2010-04-20

affects:

postfix (Ubuntu) → debconf (Ubuntu)

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-08-23:

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.