Ubuntu
msttcorefonts package

package ttf-mscorefonts-installer 3.3ubuntu3 failed to install/upgrade: aliprosessi uusi pre-installation-komentosarja palautti virhetilakoodin 128

Bug #794163 reported by Esa Vapa on 2011-06-07

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 seems to be related to restricted formats package (DVD)

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 x86_64
Architecture: amd64
Date: Sun May 29 20:46:03 2011
ErrorMessage: aliprosessi uusi pre-installation-komentosarja palautti virhetilakoodin 128
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer 3.3ubuntu3 failed to install/upgrade: aliprosessi uusi pre-installation-komentosarja palautti virhetilakoodin 128
UpgradeStatus: Upgraded to natty on 2011-05-28 (10 days ago)

Tags:

Revision history for this message

Esa Vapa (esa-vapa) wrote on 2011-06-07:

AptOrdering.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1023 bytes, text/plain; charset="utf-8")
Df.txt Edit (395 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (16.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-06-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.