HT201375: OS X: Fonts included with Mavericks

Learn about OS X: Fonts included with Mavericks
Almeister7

Q: Has anyone found a solution to the "Mavericks will not install new fonts" Issue? Has apple even admitted it yet?

Question is simple enough, Oh and by the way, my system is NOT what this forum page has decided to tell me that it is (no way evident to change it).

MacBook Pro, Macbook Pro 5,5 - OS 10.8.5

Posted on Feb 14, 2014 4:30 AM

Close

Q: Has anyone found a solution to the "Mavericks will not install new fonts" Issue? Has apple even admitted it yet?

  • All replies
  • Helpful answers

Previous Page 2
  • by Almeister7,

    Almeister7 Almeister7 Feb 15, 2014 3:48 PM in response to etresoft
    Level 1 (0 points)
    Feb 15, 2014 3:48 PM in response to etresoft

    Hi Etresoft,

     

    All updates available have been applied to CS6. Fontbook is not an Adobe product.

    Font istalls fine on other machines in our office running CS6 that are not Mavericks.

     

    Validating fonts in Fontbook is not possible for fonts that have not been installed.

  • by etresoft,

    etresoft etresoft Feb 15, 2014 4:09 PM in response to Almeister7
    Level 7 (29,258 points)
    Mac OS X
    Feb 15, 2014 4:09 PM in response to Almeister7

    It may be some other problem with Fontbook that is preventing Univers from being installed. Did you attempt to validate? The other solution specifically involved Adobe Creative Suite and the Univers font.

  • by Almeister7,

    Almeister7 Almeister7 Feb 15, 2014 4:16 PM in response to etresoft
    Level 1 (0 points)
    Feb 15, 2014 4:16 PM in response to etresoft

    Hi Etresoft.

     

    The way to validate a font in Fontbook, is you select the font, then choose 'file','validate' (To the best of my knowledge).

    This is not possible if the font is not installed.

     

    The Adobe reference in the thread that you linked to was merely (you should check for updates). This was just a red herring precaution and my Adobe products are up to date.

     

    The solution in the thread that you linked to was to validate the font. This was for a font that was already installed.

  • by HelloDavis,

    HelloDavis HelloDavis Sep 16, 2014 7:14 AM in response to Almeister7
    Level 1 (0 points)
    Sep 16, 2014 7:14 AM in response to Almeister7

    hey Almeister7,

     

    Have you solved your problem? I think its the Postscript 1 issue. I'm also trying to solve this issue too.

  • by Almeister7,

    Almeister7 Almeister7 Mar 13, 2015 4:50 PM in response to Almeister7
    Level 1 (0 points)
    Mar 13, 2015 4:50 PM in response to Almeister7

    [RESOLVED]

     

    Apologies for taking so long to get back to this with the answer. It took me a while to find this original post.

     

    Turns out it is indeed a bug with the Operating System. Apart from affecting many Mavericks Installations (fresh instal remember), it also affects some Mountain Lion Installs. I don't know about Yosemite, but after my, and my entire offices experiences with Yosemite, we have all decided to downgrade back to Mountain Lion if we can get back there, or Mavericks if that's as far back as we can go. I will leave you all to make your own decisions about pretty little Yosemite.

     

    This fix has worked for every one of the machines in our office that has been affected by this bug and for many many across the internet as well. I can't remember where I found it, but a lot of sources recommend this fix, and it worked for us, multiple times.

     

    _________________________

    FIX: DELETE FONT CACHES

    _________________________

    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 you see a progress bar towards the bottom of the screen.

     

    You can let go of the Shift key at that point.

     

    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.

     

    Not done yet.

     

    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.

     

    ____________________________________

     

    I hope this helps others that find themselves faced with this bug, as it seems to be the pretty much accepted method to deal with it.

     

    Oh, and of course, Apple still hasn't admitted to the existence of this bug,

    but that is standard operating procedure, isn't it.

     

    Cheers, and good luck.

  • by Kurt Lang,

    Kurt Lang Kurt Lang Mar 13, 2015 6:07 PM in response to Almeister7
    Level 8 (37,837 points)
    Mac OS X
    Mar 13, 2015 6:07 PM in response to Almeister7

    It's not so much a bug as a lousy font manager. Font Book's database is easily corrupted by various means. One way simply being by installing a newer OS over an older one. I see it here many times on every new release.

     

    By starting into Safe Mode (shift key restart) and then booting normally, you reset Font Book's database, which usually solves this problem.

     

    To save yourself a lot of installation time in the future, you don't need to install Mountain Lion between Snow Leopard and Mavericks. Heck, you don't need to install either of them. Create a bootable flash drive installer for Mavericks from the full download. You can then boot to the flash drive, erase the main drive and install Mavericks directly. DiskMaker X is one way to create the USB installer.

Previous Page 2