Ubuntu
mysql-dfsg-5.1 package

package mysql-server-5.1 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

Bug #550578 reported by tazzmanian on 2010-03-28

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
	mysql-dfsg-5.1 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Description: Ubuntu 9.10
Release: 9.10
Candidate: 0.22.0+fixes22594-0ubuntu1
  Version table:
     0.22.0+fixes22594-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/multiverse Packages

i expected a install but failed at 50 percent

ProblemType: Package
Architecture: amd64
Date: Sun Mar 28 19:48:52 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: mysql-server-5.1 (not installed)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: mysql-dfsg-5.1
Title: package mysql-server-5.1 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Uname: Linux 2.6.31-14-generic x86_64

Tags:

Revision history for this message

tazzmanian (whesner) wrote on 2010-03-28:

AptOrdering.txt Edit (3.7 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (48.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (12.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-03-29:

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.