every program that links to libfontconfig does not start, with the above error. i'm using emul-linux-x86-xlibs-20100915, but previous packages have the same behaviour. ldd libfontconfig.so.1 doesn't point out to any missing library. Reproducible: Always
I am unable to reproduce, please provide "emerge --info" and "layman -l" outputs
Created attachment 248826 [details] emerge --info
layman -l outputs nothing
this is what I get if I run a 32 bit app $ wine notepad.exe This version of Wine was compiled with freetype headers later than 2.2.0 but is being run with a freetype library without the FT_Load_Sfnt_Table function. Please upgrade your freetype library. I only have a 64 bit freetype library. I've reemerged freetype but only libraries from /usr/lib64/ are changeing $equery belongs /usr/lib32/libfreetype.so.6.6.0 [ Searching for file(s) /usr/lib32/libfreetype.so.6.6.0 in *... ] app-emulation/emul-linux-x86-xlibs-20100915 (/usr/lib32/libfreetype.so.6.6.0) so I can't figure out what's wrong on my system that I receive this FT_Load_Sfnt_Table error. thank you
Please follow Jakub's suggestions in http://bugs.gentoo.org/show_bug.cgi?id=195341 , maybe you have some broken and old 32 bits lib that is causing this...
And also show the following output: $ ldd /opt/firefox/firefox-bin
(In reply to comment #5) > Please follow Jakub's suggestions in > http://bugs.gentoo.org/show_bug.cgi?id=195341 , maybe you have some broken and > old 32 bits lib that is causing this... > thank you, this solved it I had an old freetype library which was located in /lib32/libfreetype.so.6 readelf -s /lib32/libfreetype.so.6 | grep FT_Load 53: 0000a9dc 643 FUNC GLOBAL DEFAULT 11 FT_Load_Glyph 173: 0000ac64 82 FUNC GLOBAL DEFAULT 11 FT_Load_Char readelf -s /usr/lib32/libfreetype.so.6 | grep FT_Load 149: 0000eca0 88 FUNC GLOBAL DEFAULT 10 FT_Load_Char 258: 000093c0 143 FUNC GLOBAL DEFAULT 10 FT_Load_Sfnt_Table 352: 0000e6d0 1479 FUNC GLOBAL DEFAULT 10 FT_Load_Glyph so I've renamed the first one, and now libfontconfig link to the second one. problem is now fixed. thank you
This bug was invalid then ;-)
(In reply to comment #8) > This bug was invalid then ;-) > yes you're right. however, I must thank you for pointing me to that bug, cause I had no idea where to look in order to solve this issue. thank you once again for your availability and kindly help