trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2010

Re: [trinity-devel] First Trinity 3.5.12 Usability Test (xset: bad font path element)

From: Darrell Anderson <humanreadable@...>
Date: Thu, 16 Sep 2010 22:19:11 -0700 (PDT)
> > xset:  bad font path element (#79), possible
> causes are:
> >     Directory does not exist or
> has wrong permissions
> >     Directory missing fonts.dir
> >     Incorrect font server address
> or syntax
> >
> > The error message is generated when startkde checks
> the font directories,
> > specifically the override directories.
> >
> > For many years this error message puzzled and annoyed
> many KDE users. Just
> > search the web and see that history.
> >
> > My location solution is not a global fix. My local
> solution is to copy
> > some font files to $KDEDIRLOCAL/share/fonts/override
> and create a
> > respective fonts.dir file.
> >
> > I would like to see this stupid error message fixed in
> Trinity --- once
> > and for all. :)
> >
> 
> Should now be fixed in revision 1176204.

If I unset my KDEDIRLOCAL and KDEDIRS variables before starting X, I still see this error message. :(