Ubuntu
msttcorefonts package

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

Bug #811785 reported by Navdeep Singh on 2011-07-17

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

Ubuntu 11.04

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ttf-mscorefonts-installer (not installed)
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Jul 16 15:43:27 2011
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
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

Navdeep Singh (navdeepsingh-sidhu95) wrote on 2011-07-17:

AptOrdering.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (448 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (123.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (13.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-07-22:

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. Please continue to report any other bugs you may find.