Oddly, they claim the problem goes away (for a while) if they
launch our app as an administrative local user and then log back
into the managed user account.
To me, that sounds like a permissions problem.
It could be permissions on the font-file itself, or on one of the
directories leading to it.
See if you can enlist one of the users where the problem occurs to
enter some appropriate 'ls -l' commands for you and send you the
output. You can also put the commands in a shell file, run it and
capture the output, then email you the resulting output file.
ls -ld /System /System/Library >~/Desktop/lsout.txt
ls -ld /System/Library/Fonts >>~/Desktop/lsout.txt
ls -ld /System/Library/Fonts/Lucida* >>~/Desktop/lsout.txt
You might also get one of the users to run a "Fix Permissions" or
"Verify Permissions" in Disk Utility.app, since I think font and font-
dir permissions would be covered.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
