bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug: font caching on OS X w/ networked home folders


From: Jacob Rundall
Subject: Re: Bug: font caching on OS X w/ networked home folders
Date: Tue, 2 Feb 2010 11:37:07 -0600

On Tue, Jan 12, 2010 at 12:39 PM, Carl Sorensen <address@hidden> wrote:

>
>
>
> On 1/12/10 10:38 AM, "Jacob Rundall" <address@hidden> wrote:
>
> > I've just checked this issue on the latest stable (2.12.3-1) and the
> latest
> > development version (2.13.10-1) and it still exists.
> >
> > Please advise when I should test again.
>
> If we had this added to the tracker (it's not, as far as I can tell;
> possibly because none of the bug-meisters can replicate it, since they
> don't
> have Macs with networked home-folders), then you could star the issue and
> you'd know if anything had been done.
>
> I've looked at this very briefly. Can you tell me what version of
> Fontconfig
> you are using?
>
Sorry for the delay.  I'm using v. 2.7.1.


>
> As far as I can see, FcConfigGetCache is used in LilyPond.  In Fontconfig
> version 2.4.0, that is correct.  In version 2.6.0 of Fontconfig,
> FcConfigGetCache is deprecated, and the description of the function
> indicates that no per-user cache file exists (see
> <
> http://developer.apple.com/Mac/library/documentation/Darwin/Reference/ManPa
> ges/man3/FcConfigGetCache.3.html<http://developer.apple.com/Mac/library/documentation/Darwin/Reference/ManPages/man3/FcConfigGetCache.3.html>
> >).
>
> Perhaps this is a Fontconfig issue, and not a networked home folders issue.
>
I'm pretty sure that networked home folders are part of the equation.  On
the same machines I can log in also with non-networked (ie local) accounts,
both admin and non-admin, and the font caching works in those cases.


>
> Thanks
>
>
> I've just verified that the issue is still there with 2.13.11-1.  Sorry
again for the delay.  I'll try to stay better tuned in.

Jake


> Carl
>
> >
> > Thanks,
> >
> > Jake
> >
> > On Tue, Dec 15, 2009 at 9:33 AM, Jacob Rundall <address@hidden>
> wrote:
> >> 2.13.9-1 exhibits the same failure to create/place the cache files for
> >> networked homefolders on OS X (10.5.8).  I will test on anything more
> current
> >> as soon as it's ready.
> >>
> >> Thanks,
> >>
> >> Jake
> >>
> >>
> >> On Mon, Dec 14, 2009 at 7:49 PM, Jacob Rundall <address@hidden>
> wrote:
> >>> It's not a problem for me to keep testing as I'm an administrator of
> two Mac
> >>> labs with networked homefolders.  I've been away from work for a few
> days
> >>> but
> >>> I'll be there tomorrow morning.  I'll test with 2.13.9-1 and if anybody
> has
> >>> a
> >>> working link for a newer version I'll try that too.
> >>>
> >>> As I mentioned in the report, the .lilypond-fonts.cache-2 directory is
> >>> created successfully, but not filled.  So I wonder if the code that
> creates
> >>> the cache files is trying to reach the homefolder by a different method
> (ie
> >>> assuming homefolders are only located in /Users for example).
> >>>
> >>> Thanks for looking into this.
> >>>
> >>> Jake
> >>>
> >>>
> >>> On Fri, Dec 11, 2009 at 10:19 PM, Patrick McCarty <address@hidden>
> wrote:
> >>>> On Fri, Dec 11, 2009 at 11:22 AM, Carl Sorensen <address@hidden>
> wrote:
> >>>>>>
> >>>>>> On 12/11/09 12:00 PM, "Valentin Villenave" <address@hidden>
> wrote:
> >>>>>>
> >>>>>>>> On Tue, Dec 8, 2009 at 6:32 PM, Jake Rundall <address@hidden>
> >>>>>> wrote:
> >>>>>>>>>> %% Font caching fails on OS X w/ networked homefolders,
> >>>>>>>>>>
> >>>>>>>>>> %% The .lilypond-fonts.cache-2 directory is created in the
> user's
> >>>>>>>>>> >>>>>> home
> >>>>>>>>>> directory,
> >>>>>>>>>> %% but the cache files do not show up there.  Performance is
> always
> >>>>>>> very slow
> >>>>>>>>>> as
> >>>>>>>>>> a result.
> >>>>>>>>
> >>>>>>>> could you try again with the latest version that's just been
> released?
> >>>>>>>>
> >>>>>>
> http://kainhofer.com/~lilypond/Documentation/web/development.html#Develop
> >>>>>> m>>>>> ent
> >>>>>>>>
> >>>>>>>> I can't reproduce it since I don't have an OSX box; Patrick, could
> you
> >>>>>>>> investigate when you have time?
> >>>>>>
> >>>>>> This may be a very difficult bug to reproduce, since it requires OSX
> with
> >>>>>> "networked homefolders", which I assume means a user with a home
> folder
> >>>>> that
> >>>>>> resides on a network drive.
> >>>>
> >>>> I can only login to OSX machines with local home folders, so I don't
> >>>> think I will be able to test this.
> >>>>
> >>>> -Patrick
> >>>
> >>
> >
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]