[Xquartz-dev] The 'official' 2.7.5 still acts the same as _rc3 and _rc4 here.

Merle Reinhart merlereinhart at mac.com
Mon Nov 11 06:28:06 PST 2013


No such issues here.  This is the 3rd machine I've put the 'official' 2.7.5 on (2 running 10.9 and 1 running 10.8).  The installer had no issues on any of those machines updating the font caches.

You do realize that to affect the font caches in the system level directories that you have to run fc-cache as root?

Merle



On Nov 11, 2013, at 7:30 AM, SciFi <sci-fi at hush.ai> wrote:

> 
> 
> 
> Hi,
> 
> 
> For the fc-cache problem still continuing:
> 
> I've run "diskutil repairPermissions /" on a login-root terminal.
> 
> Altho there were the usual suspects, there were none flagged in any/all of the font trees here.
> 
> And so I for one am still having the "fc-cache failed to write cache" messages after a perms repair.
> 
> Listing attached.
> 
> (Note I chose to use sha256sum from GNU-coreutils, the checksums do match your values.)
> 
> Other people have posted to say they've had the same "failed" message in similar circumstances.
> 
> If they still have this problem, too, after they install the official 2.7.5 pkg, then I'd say _we-all-still_ have this problem.
> 
> Again, no such failure with the _rc2/before builds.  And I'd say that-right-there is a *very*strong* clue.  ;)
> 
> … … …
> 
> I'll address the other parts later, when the xquartz.macosforge.org site comes back (it's unresponsive to me right now) and after I take a nap.  ;)
> 
> 
> 
> On 2013/11/11 03:23, Jeremy Huddleston Sequoia wrote:
>> 
>> On Nov 10, 2013, at 23:46, SciFi <sci-fi at hush.ai> wrote:
>> 
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> 
>>> 
>>> 
>>> 
>>> Hi,
>>> 
>>> I installed the 'official' 2.7.5 an hour or two ago,
>>> rather quickly after receiving your note.  ;)
>>> 
>>> It is still causing the installer messages
>>> "failed to write cache"
>>> I mentioned a few days ago.
>> 
>> ...
>> 
>> I'm not sure about the permission issue.  You should look into that on your system.
>> 
>> The perf issue that resulted in the cache being rebuilt is surely fixed:
>> 
>> ~ $ sudo /opt/X11/bin/fc-cache -v -s
>> /opt/X11/share/fonts: skipping, existing cache is valid: 0 fonts, 10 dirs
>> /opt/X11/share/fonts/100dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
>> /opt/X11/share/fonts/75dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
>> /opt/X11/share/fonts/OTF: skipping, existing cache is valid: 23 fonts, 0 dirs
>> /opt/X11/share/fonts/Speedo: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /opt/X11/share/fonts/TTF: skipping, existing cache is valid: 23 fonts, 0 dirs
>> /opt/X11/share/fonts/Type1: skipping, existing cache is valid: 29 fonts, 0 dirs
>> /opt/X11/share/fonts/cyrillic: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /opt/X11/share/fonts/encodings: skipping, existing cache is valid: 0 fonts, 1 dirs
>> /opt/X11/share/fonts/encodings/large: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /opt/X11/share/fonts/misc: skipping, existing cache is valid: 59 fonts, 0 dirs
>> /opt/X11/share/fonts/util: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts: skipping, existing cache is valid: 0 fonts, 10 dirs
>> /usr/X11R6/lib/X11/fonts/100dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/75dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/OTF: skipping, existing cache is valid: 23 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/Speedo: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/TTF: skipping, existing cache is valid: 23 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/Type1: skipping, existing cache is valid: 29 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/cyrillic: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/encodings: skipping, existing cache is valid: 0 fonts, 1 dirs
>> /usr/X11R6/lib/X11/fonts/encodings/large: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/misc: skipping, existing cache is valid: 59 fonts, 0 dirs
>> /usr/X11R6/lib/X11/fonts/util: skipping, existing cache is valid: 0 fonts, 0 dirs
>> /.local/share/fonts: skipping, no such directory
>> /System/Library/Fonts: skipping, existing cache is valid: 121 fonts, 0 dirs
>> /Library/Fonts: skipping, existing cache is valid: 505 fonts, 1 dirs
>> /Library/Fonts/Microsoft: skipping, existing cache is valid: 207 fonts, 0 dirs
>> /opt/X11/var/cache/fontconfig: cleaning cache directory
>> /.cache/fontconfig: not cleaning non-existent cache directory
>> /opt/X11/bin/fc-cache: succeeded
>> 
>> ~ $ openssl sha256 /opt/X11/bin/fc-cache
>> SHA256(/opt/X11/bin/fc-cache)= 37ffaf27187cb37206677383c64a4f1216d87c2e8ad75d162678c081a9f157f0
>> 
>> ~ $ openssl sha256 /opt/X11/lib/libfontconfig.dylib 
>> SHA256(/opt/X11/lib/libfontconfig.dylib)= 85b02448a3397e52e92abbfcac7e7f43c0981f7574db3f7068a7f7067838aa5e
>> 
>> 
>>> It is also still causing long startup times
>>> of each X11 task.
>> 
>> That is likely an issue with permissions on your system.
>> 
>>> Maybe the "relink" is still being done.
>> 
>> Nope.  It sounds like you have some permission problems.
>> 
>>> This is roughly 2-minutes after entering the command on terminal
>>> and the intended visible display of it
>>> again as I mentioned a few days ago.
>>> Perhaps it is a bit shorter than _rc3 & _rc4
>>> but it is still way longer than
>>> what _rc2 (and before) were giving us.
>>> (Yes I did let the system do a "relink after updating".
>>> It is every task after the first time, still.)
>>> 
>>> I ought to mention/remind that the
>>> "semi-stuck h/H keyboard bug" still occurs
>>> <http://xquartz.macosforge.org/trac/ticket/443>.
>>> ;)
>> 
>> /shrug ... sorry, but without a way to reproduce, there's not much chance of a fix.
>> 
>>> Shall I open a new bug report?
>> 
>> Unless someone else sees an issue, I think it might be a configuration issue on your system.  What is the output of:
>> 
>> sudo /opt/X11/bin/fc-cache -v -s
>> 
>> --Jeremy
> 
> 
> 
> 
> 
> 
> <fccache_AFTER_fixingperms(NOCHANGE)_log.txt>
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/xquartz-dev



More information about the Xquartz-dev mailing list