I have tried rebuilding the critters that font_cache and fc_cache put out.
To no avail, sadly.
Still got the "failed to write cache".
I wanted to, in effect, 'remove' the current files under each font (sub)dir
and thus start from scratch, in effect.
Here's what I did:
(under login-root terminal, mind you <g>)
(and with no XQuartz running etc)
I rm'd everything under /opt/X11/var/cache/fontconfig
(had to split-up their names on multiple rm cmds -- the 'rm *' list was too
long on my system).
Then I wanted to rename those certain files, just in case I need 'em back,
so to do this:
I cd'd to the various font directories, one at a time, then did this at each
one to rename them:
# find . -name 'encodings.dir' -exec mv '{}' '{}'_orig \;
# find . -name 'fonts.dir' -exec mv '{}' '{}'_orig \;
# find . -name 'fonts.list' -exec mv '{}' '{}'_orig \;
# find . -name 'fonts.scale' -exec mv '{}' '{}'_orig \;
(that worked fine with the GNU-coreutils version)
Lastly I ran:
# /opt/X11/bin/font_cache -f -v -s
Sho'nuf, it put out lots of lines saying "failed to write cache".
I compared the 'new' files to the 'renamed/old' ones,
and the sizes at least were not the same, at all.
Oh well. Qué Será, Será … I guess.
I'm going to use these new files for XQuartz_2.7.5 now.
Cogitatin'…
I am now wondering, that since Peter Dyballa seems to demonstrate the same
problem, if it could be the use of Case-SENsitive volumes perhaps a culprit?
I might also try cloning the fontconfig git repo to pick-up all those patches
on the master tree since 2.11.0 came out. I then should consider joining their
mail-list and/or opening a(nother) bug on this.
I need to reiterate to Merle Reinhart and others that I am still using 10.6.8
with all security updates (I mentioned this at the start of the original thread
[_rc3 & _rc4]) -- and I use Case-SENsitive setting on all my volumes (we have
over 100 HDDs full of TV archives from HDHomeRun boxes and EyeTV; I'm now using
4TB drives, believe it or not <g>).
I did do some research on this problem (using IXQuick.com [for security
reasons]) -- turns out, over the years, this is a widely-known problem with
several platforms and languages/countries, not just OSX.
Here's one hit that seems to be sort-of recent (at the tail end of this thread):
<https://bugzilla.novell.com/show_bug.cgi?id=227385>
No hits ever did say exactly how they fixed this, short of re-installing
everything from scratch (good-lawdy I have accrued _so_ much here, I can only
feel safe by backup-&-restore the boot volume y'know <g>).
I'll stay tuned for any thoughts on this.
Thanks for reading and helping if possible.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xquartz-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/xquartz-dev
