libXfont, dixfonts.c, and all the associated mess is just a litany of horror. we should ... do something else. anything. to give just one example, where all four are valid font paths, but the ones under ~ are empty: daniels@endtroducing:~/src/control-center-2.14.1/gnome-settings-daemon% xset fp /usr/share/X11/fonts/misc:/usr/share/X11/fonts/100dpi:/home/daniels/.gnome2/share/cursor-fonts:/home/daniels/.gnome2/share/fonts daniels@endtroducing:~/src/control-center-2.14.1/gnome-settings-daemon% xset fp /home/daniels/.gnome2/share/cursor-fonts:/home/daniels/.gnome2/share/fonts:/usr/share/X11/fonts/misc:/usr/share/X11/fonts/100dpi xset: bad font path element (#60), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax zsh: exit 255 xset fp woo!
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Daniel Stone Do you still experience this issue with newer soft ? Please check the status of your issue.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/343.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.