The ProFont x11 font from tobiasjung.net (http://www.tobiasjung.net/download.php?file=profont-x11.tar.gz) worked in freetype versions <=2.1.7, but not in >=2.1.9. It shows up as a font in font lists but does not actually display as a font (in gnome font pickers it displays as sans-serif), and when Firefox tries to use it, instant segfault. I have it set as my monotype font in Firefox, and when I type one letter in a monospaced field, there goes firefox. This may be a problem with the font itself and I have yet to try to re-encode it, but besides that there must be a difference between 2.1.7 and 2.1.9[-r1] that breaks compatability of certain bitmap fonts. Reproducible: Always Steps to Reproduce: 1. Download / install the font 2. Open either gnome-font-properties, kcontrol, or Firefox and try to use it Actual Results: gnome-font-properties/kcontrol->appearance->fonts displays the system sans-serif font, Firefox segfaults upon attempting to display a character Expected Results: Use the font correctly ;) 2.1.9-r1 does indeed fix the corrupted fonts, but not this problem. # emerge info Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-rc3 i686) ================================================================= System uname: 2.6.10-rc3 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Dec 21 2004, 21:14:26)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=prescott -fomit-frame-pointer -ftracer -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=prescott -fomit-frame-pointer -ftracer -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://lug.mtu.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3ds X Xaw3d acl acpi adns aim alsa apache2 arts audiofile avi berkdb bitmap-fonts cairo cdparanoia cdr crypt cups dba dvd dvdr encode esd fam flac flash foomaticdb fortran freetype ftp gb gd gdbm gif gimp gimpprint gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal icq imagemagick imlib ipv6 jabber jack java joystick jpeg jpeg2k junit kde ladcca ldap libwww lm_sensors lzw-tiff mad mbox mhash mikmod mmx mng motif mozdevelop mozilla mozsvg mp3 mpeg msn mysql ncurses nls nptl nvidia objc offensive oggvorbis opengl pam pcmcia pdflib perl php png ppds python qt quicktime readline samba sdl slang socks5 speex spell sse sse2 sse3 ssl svg svga tcltk tcpd tga theora tidy tiff truetype truetype-fonts trusted usb userlocales v4l v4l2 wavelan wmf wxwindows xgetdefault xine xml xml2 xmms xosd xrandr xscreensaver xv yahoo zlib"
This problem was fixed by re-encoding the font, but you still have to wonder, what changed? Everyday users won't know how to re-encode a font just to make it work again, so I myself still consider this a bug.
what do you mean by re-encoding ? remerging & going trough the font creation steps ? I also have sets of bitmap fonts, but no problems here with them. If it crashes we need a backtrace.
By re-encoding I mean actually decoding the font to BDF with FontForge and then re-encoding it to PCF with bdftopcf.
this seems to be an ABI issue with freetype 2.1.9, not sure what we to do about it. Apparently it doesn't hit all fonts bdf to pcf fonts, x11 has quite a few of them.
I tested profont and it works fine here, firefox displays it correctly and doesn't crash (same for other apps). I think this can be closed with NEEDINFO, unless someone's still using a 2 year old fontconfig :)
The reason why it works is because I actually modified ProFont and sent the author the changes and it is now the "official" Linux profont version that you have ;) Bug can be closed at least in the case of ProFont, however I'm not sure how many older fonts are still broken.
Closing then, noone else reported this w/ any other font.
