As you can read in this¹ thread, the Xorg server expects a number of font paths given, throwing some pointless warnings otherwise, so they should probably be added with keepdir - in media-fonts/font-alias perhaps!? Looking at my /usr/share/fonts/ directory, we install them all in the basedir, while Xorg expects /usr/share/fonts/{misc,TTF,OTF,Type1,100dpi,75dpi}. Guess it makes sense to follow the de facto standard. [1] http://forums.gentoo.org/viewtopic.php?p=4709564#4709564
"Could not connect to the database" <-- so much for phpBB boon... xorg-server just discards the non-existant ones from FontPath; why should we be creating such junk for the sole purpose of making the logs shut up?
(In reply to comment #1) > xorg-server just discards the non-existant ones from FontPath; why should we be > creating such junk for the sole purpose of making the logs shut up? Exactly. Could you please stop with these irrelevant comments, please. It's maintainer's business, not yours.
(In reply to comment #2) > Exactly. Could you please stop with these irrelevant comments, please. It's > maintainer's business, not yours. What's irrelavant about my comment? If you complain about xorg-server expecting some paths to exist, then damn take it upstream instead of nagging overloaded maintainer with upstream non-issues.
Relax. :) We'll look and decide severity for ourselves.
(In reply to comment #3) > What's irrelavant about my comment?. Your opinion does not matter. Leave it to the maintainers. This last time I'm going to explain it for you: I do not complain, I noticed a user having basically a "non-problem" and filed this bug, because I sensed he wouldn't. Why?! Because he will be not the only one wondering about this issue. Such invalid/pointless/misleading warnings waste users a lot of time. It's a sign of bad quality on our side. Once again Jakub: Learn to take yourself back. As a bug wrangler your opinion doen't matter. You don't have to comment on every stupid bug, spamming inboxes. Get yourself a blog, if you need to. Too often I did not reopen a bug you did resolve wrongly, just because I'm sick of dealing with your behaviour in bugzilla.
current output vs expected output missing... I guess it's Could not init font path element /usr/share/fonts/TTF/, removing from list! Could not init font path element /usr/share/fonts/OTF, removing from list! Could not init font path element /usr/share/fonts/Type1/, removing from list! Could not init font path element /usr/share/fonts/100dpi/, removing from list! Could not init font path element /usr/share/fonts/75dpi/, removing from list! Patching the default font path could be a solution, still I consider it as an enhancement since it has no effect beside adding 5 lines in the log.
(In reply to comment #5) > Such invalid/pointless/misleading warnings waste users a lot of time. It's a > sign of bad quality on our side. The warning isn't invalid nor misleading, it's perfectly valid for that matter as the path doesn't exist. It's just completely harmless couple of lines in a log. Maybe people would like to have loglevel setting for xorg-server but that's something that needs to go upstream. I have commented on this bug because the proposed solution didn't make any sense at all. (And take your off-topic rants out of this bug please). (In reply to comment #6) > current output vs expected output missing... $ grep "Could not init font path element" /var/log/Xorg.0.log $ /etc/X11/xorg.conf <snip> # FontPath "/usr/share/fonts/TTF" # FontPath "/usr/share/fonts/freefont" # FontPath "/usr/share/fonts/local" # FontPath "/usr/local/share/fonts" # FontPath "/usr/share/fonts/Type1/" # FontPath "/usr/share/fonts/CID/" # FontPath "/usr/share/fonts/Speedo/" # FontPath "/usr/share/fonts/TrueType/" # FontPath "/usr/share/fonts/freefont/" </snip> is what I have commented out (years ago) so some of those might not even exist as default any more (and I definitely do not want them created via keepdir).
BTW - Option "UseDefaultFontPath" "no" just disables this altogether if you dislike it so much (certainly undesired as default value in xorg.conf though).
i don't see how this is any different than the other crapload of warnings in the Xorg log. the OP is concerned about an attempted load at Xorg start? it's one stat call. if they were keepdir'd you'd have the overhead of fontconfig scanning and caching the contents of these (empty) dirs every time a font is installed or uninstalled. both are minuscule, but if you want to compare...
