Ubuntu
msttcorefonts package

package ttf-mscorefonts-installer (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 128

Bug #778483 reported by Alessandro Cresto Miseroglio on 2011-05-06

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

.....

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ttf-mscorefonts-installer (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri May 6 14:14:23 2011
ErrorMessage: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 128
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Alessandro Cresto Miseroglio (alex179ohm) wrote on 2011-05-06:

AptOrdering.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Df.txt Edit (382 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (61.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (8.5 KiB, text/plain; charset="utf-8")

Ubuntu Foundations Team Bug Bot (crichton) on 2011-05-06

affects:

ubuntu → msttcorefonts (Ubuntu)

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.