msttcorefonts failed to install. System reported the activity had crashed.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| msttcorefonts (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: msttcorefonts
Ubuntu 8.10 msttcorefonts 2.5
Attempted to download and install package using "add/remove". Should have just downloaded and installed automatically.
The download/install started ok, but after some minutes the terminal window started to show "time-outs" and failure to complete on some of the fonts. Eventually, a warning flag popped up to inform me that the process had "crashed". After several more minutes, the terminal window showed the process had given up with multiple failures. I closed the terminal and went back to "add/remove" to retry the download. The package was shown as installed (tick in box) so attempted to remove the packge by un-ticking the box. After multiple attempts, the system advised me to go to terminal with two messages 1. "E: dpkg --configure -a
and 2. E:cache ->open () failed.
I went to the terminal and invoked "sudo dpkg --configure -a" which restarted the download process in the terminal and it completed properly.
NB. I am a newbie so any queries to me in plain non-technical English please. :-))
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: msttcorefonts 2.5
PackageArchitec
SourcePackage: msttcorefonts
Title: package msttcorefonts 2.5 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.27-9-generic i686
| Tony Deacon (tonydeacon27) wrote | #1 |
| goto (gotolaunchpad) wrote | #2 |
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 305963, 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.