I have noticed that Mozilla configured with --enable-xft links with libXft.so.1, but apparently wants libXft.so.2 from fontconfig (it fails to start with libXft.so.1 because XftLockFace symbol is not resolved). Maybe this is problem of my system configuration (libXft.so points to libXft.so.1) but anyway I think it is a Bad Thing (tm).
Assignee: font → blizzard
[blizzard@dead blizzard]$ ldd /usr/lib/mozilla-1.2b/components/libgfx_gtk.so |grep Xft libXft.so.2 => /usr/lib/libXft.so.2 (0x4050f000) Looks fine here. Something odd going on on your system, maybe?
Yep, libXft.so pointed to libXft.so.1 instead of so.2. Sorry.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
Maybe there ought to be a specific check that the library is in fact Xft2 (or later) and not Xft1. Most people still have (either the old or new version of) Xft1 along with Xft2 on their systems, and it's possible that libXft.so could be linked to Xft1, but that's not what Mozilla needs.
Mark as verified per above 2 comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.