Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Font Book crashes when trying to remove corrupt fonts

I have recently upgraded to Snow Leopard and am having problems with my fonts.

After installing some of my previously used fonts, some of them didn't pass validation. I don't mind removing them - I barely use 1% of the fonts I have, but when I run Font Validation in Font Book and then select all the corrupt files and click "Remove" - Font Book just gets stuck.

Then I went by the list and removed MANUALLY all the invalid font files (the ones with the red cross sign).

Then only the minor warnings remained , but even when I try to remove them with Font Book - it still crashes.

It's ridiculous to remove them manually one by one, cause I have a huge collection of 1000s of fonts and there are more than 500 corrupt fonts there. I'm not using many fonts, but I want to keep my library up and working, so I want to get rid of everything that might cause problems...

Any help?

MacBook Pro, Mac OS X (10.6.8)

Posted on Jul 22, 2012 5:20 AM

Reply
Question marked as Best reply

Posted on Jul 22, 2012 6:57 AM

Font Book's database has been trashed. What you see happening is a common symptom.


First manually delete all fonts from the Fonts folders they reside in you don't want in there. Then reset Font Book.


Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Keep holding the Shift key until OS X asks you to log in (you will get this screen on a Safe Mode boot even if your Mac is set to automatically log in). Let the Mac finish booting to the desktop and then restart normally. This will clear Font Book's database and the cache files of the user account you logged into in Safe Mode.


You should also then clear the font cache files from the system.


Close all running applications. From an administrator account, open the Terminal app and enter the following command. You can also copy/paste it from here into the Terminal window:


sudo atsutil databases -remove


Terminal will then ask for your admin password. As you type, it will not show anything, so be sure to enter it correctly.


This removes all font cache files. Both for the system and the current user font cache files. After running the command, close Terminal and immediately restart your Mac.


Once that restart is complete, now launch Font Book so it can create a new database based on the fonts which you left on the drive.

25 replies

Sep 1, 2012 6:13 AM in response to Kurt Lang

When I need to keep working, but get a clean install of everything going, I do it all on a spare drive or partition as I have time. It gets done eventually without bringing you to a standstill.

Kurt, please tell me a bit more about this procedure. Never did a clean install on Mac on a spare drive, while working on the main one...

Can I install the OS on another drive while keeping working on the same computer?

How then I migrate all my system to my main drive?

Will I be able to restore files from Time Machine from a backup that was made in Leopard? (just in case)...

Thanks

Sep 1, 2012 6:49 AM in response to danas_blia

danas_blia wrote:


I am using a standard Lithuanian keyboard layout provided by Apple and I was using exactly the same in Leopard


Apple's Lithuanian keyboard only works with Unicode fonts. If they worked before, they should work now. If you ever used non-Uncode (most likely old PS) fonts, then these would either use the US layout or require a custom layout, and it's possible such fonts may stop working at all.


So you really cannot type Lithuanian in TextEdit with Apple's keyboard?

Sep 1, 2012 7:21 AM in response to Tom Gewecke

Apple's Lithuanian keyboard only works with Unicode fonts. If they worked before, they should work now. If you ever used non-Uncode (most likely old PS) fonts, then these would either use the US layout or require a custom layout, and it's possible such fonts may stop working at all.

They did work before. Maybe not all of them, but at least they worked all fine in InDesign ME, which as I realised before, can use also non-unicode fonts and make them type correctly...

So you really cannot type Lithuanian in TextEdit with Apple's keyboard?

I can type Lithuanian perfectly, but not with those fonts - that's what I meant.

So now I have a collection of over a 1000 fonts, that is what - useless??? I do need them - I have many projects with those fonts... I obviously cannot be limited to using the standard system fonts only?!

Sep 1, 2012 8:32 AM in response to danas_blia

Kurt, please tell me a bit more about this procedure. Never did a clean install on Mac on a spare drive, while working on the main one...

In short, you're just using a separate erased drive/partition to install the OS and your apps from scratch.

Can I install the OS on another drive while keeping working on the same computer?

Yes, that's what I do. You can install OS X on as many separate drives/partitions as you have.


What I do is gradually work my way into a new OS. Like right now, I'm still doing all of my real work in Snow Leopard, while on a separate drive mounted in my Mac Pro, I have Mountain Lion installed. That way, I can keep an eye on updates and see how the OS progresses and initial bugs are worked out.


When I was moving from Leopard to Snow Leopard, SL was a complete rewrite to full 64 bit. 10.6.0 was loaded with major issues that made it unusable for production work. Fonts, especially Type 1 PostScript, were a complete mess. ColorSync was way off. It took until 10.6.3 for SL to be ready for real work. But it didn't bother me. I kept working from the main drive in 10.5.x as I kept an eye on SL's progress.


That's what I'm doing with Mountain Lion (I skipped Lion completely). Some tools I need still don't work, or haven't yet been updated for ML. Overall though, it appears to be a very clean OS. So I'm still in watch mode as I continue to use Snow Leopard day-to-day.

How then I migrate all my system to my main drive?

By "system", I presume you mean the rest of your third party apps and personal data? If so, I never move those, either. The purpose is to keep the drive completely clean. I reinstall all apps I use from scratch onto the new OS. I don't want any garbage, damaged files, old OS files or prefs brought over. The few I will copy from my current drive is things like all of the preference files from my user account for the Adobe apps so I don't have to set all of my palettes and preferred settings all over again. Otherwise, pretty much everything else gets left behind.

Will I be able to restore files from Time Machine from a backup that was made in Leopard? (just in case)...

You can, but I don't use Time Machine, so can't say exactly how that would work. If it just copies over everything that doesn't exist onto the new OS, then you've defeated the purpose of leaving old, outdated, or possibly corrupt data behind. Pick and choose from the TM backup to only bring in what is absolutely necessary. Which of course is any files you've created, your email data and other specific items. That does mean though that you need to know where this stuff is in the first place. Rather hard to do if you don't.

Sep 1, 2012 2:55 PM in response to danas_blia

Thanks for sending the font!


It is a non-Unicode version from 1996. If you try to input Lithuanian special characters from it using Apple's Lithuanian keyboard, you will either get nothing or the correct character taken from another font, depending on the app. If you happen to have a Unicode version of the same font on your machine, it would probably all look correct.


If you only have the non-Unicode version of that font, to input the special characters you would use the Apple US (or actually preferably the Icelandic) keyboard layout and pretend you were inputting something else. The graphic below shows standard input in Arial and the result when you switch to the non-Unicode font. Some apps may not do this very well, I used OpenOffice.


User uploaded file

Sep 2, 2012 12:18 PM in response to Tom Gewecke

Hah, that's all very weird, cause they did work as supposed to in Leopard... maybe Leopard had a glitch, that could read and interpret older encodings?


Unfortunately the workaround with using another keyboard layout to input the Lithianian characters wouldn't satisfy me, because I often get texts, that already are typed in and I just paste them, so it would become a mess... Besides - I didnt manage to find how to type them with the Icelandic or American keyboard eyther - how did you do it?


Don't know about the missing characters - probably they saved time on unnecessary stuff??


Is there a way to convert a font to a unicode font?

Sep 2, 2012 2:41 PM in response to danas_blia

danas_blia wrote:


I didnt manage to find how to type them with the Icelandic or American keyboard eyther - how did you do it?



With OpenOffice and the US keyboard, I set the font to Century Gothic and then typed option/alt + `, then a. With normal fonts this produces à, with Century Gothic it produces ą .


You can convert fonts with a font editor, like FontLab or FontForge, but they are not very easy to use.

Sep 4, 2012 1:02 PM in response to Kurt Lang

By "system", I presume you mean the rest of your third party apps and personal data? If so, I never move those, either.

No no - I mean after I'm done installing the system to an external drive, how do I move it to the main harddisk (of course, assuming I did a full backup of all my files, so I'm ready to have the new system on my computer).

Font Book crashes when trying to remove corrupt fonts

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.