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

Bug #966924 reported by K. Aning
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
msttcorefonts (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happened on login not sure why because I thought I installed this about 2 or 3 days ago

lsb_release -rd
Description: Ubuntu Precise (development branch)
Release: 12.04

Package: package ttf-mscorefonts-installer 3.4ubuntu2

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ttf-mscorefonts-installer 3.4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Sat Mar 24 21:11:36 2012
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
PackageArchitecture: all
SourcePackage: msttcorefonts
Title: package ttf-mscorefonts-installer 3.4ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
K. Aning (constrictor) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Brian Murray (brian-murray) wrote :

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.

Revision history for this message
Steve Langasek (vorlon) wrote :

Bug #722049 is itself marked a duplicate of bug #442941, which has been marked resolved in precise. So either this isn't the same bug, or it's not really fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.