The configure script of libXfont contains an 'enable-type1' option, which is later required for Type1 font support to work in the xserver. With x11-base/xorg-server-1.1.1-r3 I therefor see in the Xorg.0.log: (II) Loading extension GLX (II) LoadModule: "type1" (II) Loading /usr/lib64/xorg/modules/fonts/libtype1.so dlopen: /usr/lib64/xorg/modules/fonts/libtype1.so: undefined symbol: Type1RegisterFontFileFunctions (EE) Failed to load /usr/lib64/xorg/modules/fonts/libtype1.so (II) UnloadModule: "type1" (EE) Failed to load module "type1" (loader failed, 7) (II) LoadModule: "freetype" and Type1 fonts subsequently don't work as expected. There also is no way to actually disable the Type1 font support in the xserver through use flags or the like. Of course it's possible to comment out the Load "Type1" from the xorg.conf, but that's not a real solution. For that reason I've added a 'type1' use flag to the libXorg ebuild, as already existing for kdrive, and the error went away: (II) Loading extension GLX (II) LoadModule: "type1" (II) Loading /usr/lib64/xorg/modules/fonts/libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Type1 (II) LoadModule: "freetype" Someone please check if there are other RDEPENDS or requirements which I did miss, but so far this works ok.
Created attachment 103735 [details] modified ebuild for libXfont
The freetype module is supposed to render the Type1 fonts instead of the type1 module. What issues did you have with Type1 fonts after the switch to 1.2.5?
(In reply to comment #0) > Of course it's possible to comment out the Load "Type1" from > the xorg.conf, but that's not a real solution. Why isn't it?
(In reply to comment #3) > (In reply to comment #0) > > Of course it's possible to comment out the Load "Type1" from > > the xorg.conf, but that's not a real solution. > > Why isn't it? > The problem I had was that we now build (unconditionally) an xserver module which relies on a feature of libXfont for which we no way to enable, resulting in an unresolved symbol for the possible user. Commenting out the "Type1" module load _is_ away to get rid of that, but still leaves the non-working module in the build. As long as I also load "freetype" I indeed have no issue with Type1 font rendering (Joshua comment #2). The whole discussion is mood however, as freedesktop git shows that libXfont 1.2.6 will have Type1 support enable by default and the added useflag therefore is not required any more. So once libXfont 1.2.6 is in portage this can be closed.
1.2.6 has been committed. Thanks for sticking with this!