screwed up install
Bug #316646 reported by
uc12345678
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ttf-unfonts (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ttf-unfonts
I have no idea
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 139
Package: ttf-unfonts-core 1.0.1-7ubuntu1
PackageArchitec
SourcePackage: ttf-unfonts
Title: package ttf-unfonts-core 1.0.1-7ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 139
Uname: Linux 2.6.27-7-generic i686
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
The relevant error was: fonts/truetype/ unfonts Regular- JaH, defaulting to 0. Regular, defaulting to 0. Regular, defaulting to 0. Regular- JaH, defaulting to 0.
---
Updating fontconfig cache for /usr/share/
No CIDSupplement specified for Batang-Bold, defaulting to 0.
No CIDSupplement specified for UMingCN, defaulting to 0.
No CIDSupplement specified for KochiGothic-
No CIDSupplement specified for Dotum-Bold, defaulting to 0.
No CIDSupplement specified for KochiMincho-
No CIDSupplement specified for KochiGothic-
No CIDSupplement specified for KochiMincho-
No CIDSupplement specified for Dotum-Regular, defaulting to 0.
No CIDSupplement specified for Batang-Regular, defaulting to 0.
Segmentation fault
dpkg: error processing ttf-unfonts-core (--configure):
subprocess post-installation script returned error exit status 139
This kind of error is likely due to a corrupted memory. If it happens frequently you should run the "Memory check" from the boot menu. If that runs successfully, please start the rescue system in the boot menu and select the "File system check" option in the next menu
I'm closing this report because you reported this bug a while ago and there is no recent duplicate nor user mentioning having the issue on Karmic. If this is still an issue, don't hesitate to reopen the report. Thanks again!