Online forums recommend full OS X reinstall in somewhat Windows-horror story like scenario. It is also possible that these fonts are stored in your user profile, because of that Keynote will not crash if you create a new user and try running it from there. This does not seem to affect any applications normally so you can survive a long time before you run the Keynote for first time and it crashes. When I installed Leopard I updated my Tiger installation which it seems to transfer some fonts and thus create duplicates. Taking a minute to think of the scenario that created environment for this crash.
After OS X reboot your system will automatically rebuild the font cache.Īt this point, you can try running Keynote or any other crashing application again and it should work as in good old Tiger days.
FONTNUKE DOWNLOAD MAC UPDATE
After you run it, first Update Cache List and then Nuke Font Caches. You can always turn them on later if you decide that you need the other font from the duplicated pair.ĭownload neat little utility called Font Nuke (it’s free). This will automatically disable one of the fonts in duplicate fonts pairs. You can then either manually turn off conflicting fonts or choose Resolve Duplicates from Edit menu. In my case I had a few dozens of duplicates on the system. This means that you have duplicates of this font installed. Once you have Font Book open, check for any fonts that have black dots next to the name. *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: (index >= 0) & (index Font Book) Download WhatsApp on your mobile device, tablet or desktop and stay connected on across your devices, so you can pick up any conversation where you left off. Some time after installing Leopard OS X 10.5 and second set of updats for iWork 08 the Keynote Application started crashing on start.
0 kommentar(er)
