Bitmap fonts (at least the fixed font) seem to be broken in xorg-server-1.6.0. The behaviour is the same as for 1.5.3 reported and fixed here: http://bugs.gentoo.org/show_bug.cgi?id=255082 Is the fix missing in xorg-server-1.6.0 or does it have to be fixed differently?
1.6.0 is indeed missing that patch. I've pinged upstream about it and hopefully it should be there in 1.6.1. Thanks
I've nominated this patch for inclusion in the 1.6 branch, hopefully this will make it into 1.6.2. Cheers
Well it looks like I was wrong all along, that patch has been in the 1.6 branch since xorg-server-1.5.99.903 ... Could you please get back to us with a fresh Xorg.0.log from 1.6.1.901 or newer? Thanks
Created attachment 191699 [details] Xorg.0.log
I'm lost. The exact same code is in both versions of xorg-server. I'm thinking there's another bug... Could you please completely describe your issue (let's not compare with bug #255082). Thanks
After writing the text describing the problem I tried something else before submitting it: I readded the FontPath lines for the bitmap fonts to xorg.conf and everything worked as expected. I thought they aren't needed anymore.
Depends what you mean by "needed". We mean that they are no longer needed because xorg-server now has a builtin version of the "fixed" font. It looks ugly and it only has one size, but it should allow all apps that rely on Core fonts to work properly. But if you do want to use Helvetica or other Adobe font files, then you need to install them and to make sure that your FontPath picks them up. Thanks
As I see it, there are standard font directories, which are used, when nothing is specified, and although the man page says that there are all in /usr/lib/X11/fonts (maybe the man pages is out of sync), it worked flawlessly in xorg-server-1.5.3 (after patching the bug), so all the fixed variations and helvetica were in the correct directories. But now it does not work and I have to specify the directories by hand, which imho is a regression. It also contradicts the goal of eliminating xorg.conf for common cases. Now I have one more reason to keep it.
Right, there should be a default path other than just "built-ins", I don't know how it got stripped. I'll look into it when I can. Reopening Thanks
Found it, the ebuild was simply changing the default font path to just "built-ins". I had indeed fixed that for 1.5 but not for the other ebuilds in the x11 overlay. 1.6.1.901-r2 should now behave properly and set a "reasonable" FontPath by default. Please don't hesitate to reopen this bug if you still have issues. Thanks
