Ubuntu
msttcorefonts package

package ttf-mscorefonts-installer (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

Bug #746705 reported by kacer2k on 2011-03-31

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
	msttcorefonts (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: msttcorefonts

I don't know anything.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ttf-mscorefonts-installer (not installed)
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Mar 31 22:13:13 2011
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

kacer2k (juancarlosvicente) wrote on 2011-03-31:

AptOrdering.txt Edit (4.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (55.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (15.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-16:

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 #722049, 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. Feel free to continue to report any other bugs you may find.