Ubuntu
msttcorefonts package

package ttf-mscorefonts-installer 3.3ubuntu3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

Bug #780262 reported by Vallin Dayton Estes, Jr. on 2011-05-10

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

Just had trouble signing in to Ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ttf-mscorefonts-installer 3.3ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Mon May 9 19:27:41 2011
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110422)
PackageArchitecture: all
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer 3.3ubuntu3 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

Vallin Dayton Estes, Jr. (vallin-estes) wrote on 2011-05-10:

AptOrdering.txt Edit (928 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1023 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (38.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (10.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Andrew Constantine (andrewmc) wrote on 2011-05-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 756750, 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.