Weird Font Issues – Photoshop CS4 – Possible fontd issue?

[dead2sin]

I’ve build several snow leopard images recently using InstaDMG 1.5 RC1 and I’ve noticed something rather interesting.

I have a package that installs CS4 on the workflow (I rebuilt it especially for snow leopard and updated it).

When you boot the image and open photoshop, the fonts that get installed with the app are not available in photoshop. They are present in /Library/Fonts and they are in Fontbook. I’ve tried disabling/enabling them using fontbook, using the atsutil command as well as just moving them out and putting them back.

I cannot get the fonts to show up in CS4 on Snow Leopard no matter what I do. Its quite the situation.

I troubleshot the situation over the course of the last week and it has not been fun. I’ve made a plain jane vanilla image using the 10.6 Vanilla catalog and installed Photoshop using the originally installer. Guess what? Fonts STILL don’t show up in Photoshop!

I’m not sure how I can fix this issue…I never had any issues with it on 10.5 that I know of (I’m going to go back and double check). I’ve tried 1.5 RC1, 1.4b4, chroot on, chroot off, with 10.6.1, without 10.6.1, plain vanilla image using the official adobe installer, everything!

If we install off the Retail CD and install photoshop, it works fine. If I take an image of that exact same retail CD and run the vanilla catalog on it and generate a vanilla image, it no longer works. It seems to be an InstaDMG issue, but I am not sure how to even prove that.

Any suggestions? Anyone run into this before? This is holding me up from deploying a Snow Leopard image and I’d sure like to figure out what the heck is causing it.

[dead2sin]

Also, I noticed using 1.5 RC1 that I get crazy dyld shared cache errors when making images. The system log shows that this is playing into the fontd issue. Here is an example:

[code]
ov 9 11:03:57 localhost com.apple.fontd[102]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 11:04:23 localhost com.apple.fontd[102]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 11:04:24 localhost /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[102]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:07:16 netboot003 com.apple.fontd[208]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:16 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[208]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:07:52 netboot003 com.apple.fontd[251]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:52 netboot003 com.apple.fontd[251]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:52 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[251]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:09:46 netboot003 com.apple.fontd[355]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:09:48 netboot003 com.apple.fontd[355]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:09:49 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[355]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
[/code]

Why is there a dyld cache in place if its never been booted? And if it is created, should it not be deleted before the image is finished?

Thanks,

Nate

[walt]

See this thread to resolve the dyld shared cache issue.

[url]https://www.afp548.com/forum/viewtopic.php?showtopic=25426[/url]

Hopefully that fixes your problem.

[dead2sin]

[QUOTE][u]Quote by: walt[/u][p]See this thread to resolve the dyld shared cache issue.

[url]https://www.afp548.com/forum/viewtopic.php?showtopic=25426[/url]

Hopefully that fixes your problem.[/p][/QUOTE]

I’ve been doing that on my images, but it doesn’t fix this issue. I’m going to look at the instadmg.bash script and see about adding some lines in the cleanup that delete the dyld cache. Perhaps that will fix it.

[dead2sin]

This is pretty urgent issue as far as Snow Leopard InstaDMG builds go. The dyld issue is fixed (thanks walt!), but the fontd issue remains. It prevents Photoshop from using any of the fonts it installs.

This is the error that keeps repeating:

[code]Nov 9 14:07:52 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[251]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.[/code]

Anyone else run into this error in their system log? I’ve tried using the atsutil to remove the database and generate a new one, but it still gives that error. I don’t get this error whilst using a fresh install off of DVD, as I mentioned before.

Any suggestions are welcome!

[dead2sin]

10.6.2 just came out and it mentions some font fixes. Perhaps it was really an issue with 10.6.1. I’ll update this thread if 10.6.2 fixes the issue.

[dead2sin]

10.6.2 did not fix the issue. Still getting the errors above when building images.

[akinspe]

I had a similar problem. I added a /usr/sbin/diskutil repairPermissions “$TARGET_IMAGE_MOUNT” to the build train and it fixed those fontd issues. My rough estimation was that it had to do with the permissions of the /Library and specifically /Library/Caches

[dead2sin]

[QUOTE][u]Quote by: akinspe[/u][p]I had a similar problem. I added a /usr/sbin/diskutil repairPermissions “$TARGET_IMAGE_MOUNT” to the build train and it fixed those fontd issues. My rough estimation was that it had to do with the permissions of the /Library and specifically /Library/Caches
[/p][/QUOTE]

You sir are my new hero. Thank you VERY much! I couldn’t find a thing using google, but this has solved the problem.

Nate

[Author]

Posts