Ubuntu
msttcorefonts package

package ttf-mscorefonts-installer (not installed) failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 128 zurück

Bug #722596 reported by Gieseler on 2011-02-21

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

it happens while updating

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: ttf-mscorefonts-installer (not installed)
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Feb 20 11:15:58 2011
ErrorMessage: Unterprozess neues pre-installation-Skript gab den Fehlerwert 128 zurück
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer (not installed) failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 128 zurück

Tags:

Revision history for this message

Gieseler (gieseler-westenholz) wrote on 2011-02-21:

AptOrdering.txt Edit (942 bytes, text/plain; charset="utf-8")
Df.txt Edit (460 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (35.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (51.3 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.