If you have freetype-2.1.9 or freetype-2.1.9-r1 installed you will most likelly experience many problems with mozilla and it's derivatives. Your browser behavior ranges from unexplained crashes on certain pages to who knows what. Basically all browsers based on the gecko engine become unusable. There is a huge urge from many users to install a newer version of freetype because gimp-2.2 would not run with 2.1.5 and this is why many people have been complaning about the mozilla/firefox crashes and segmentation faults. I did a thorough testing of the issue since I was also affected by it and found out that freetype was actually responsible for the crashes. I am not very familiar with freetype but since a browser is one of the most used applications on any desktop this is major feature being broken and the problem should some how be addressed or at least explained. Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is being discussed in #71809 as well, I think the problem is the X.org 6.7 + freetype >2.1.5 combo. The best solution would be to add some sort of test to all gecko-based browser ebuilds to warn or block the merge if X.org 6.7 and Freetype >2.1.5 is installed.
It is very possible that the bug is with xorg 6.7 + >freetype-2.1.5 because I also have xorg 6.7 installed. I can't really check if xorg has anything to do with this because my ati drivers do not work with xorg above 6.7.
it shouldn't -- there's patches in moz* to compile against 2.1.9. You probably have to remerge them, that's all. As of now, the only package which doesn't have that compatibility patch is gecko-sdk
I don't know if there is a patch but if there is it most deffinitelly does not work. I have recompiled the software is any imaginable configuration and moz* with freetype >2.1.5 does not work well at all.
This is staring to be a major annoyance and if it doesn't get resolved there is no way that gimp 2.2 will ever work because every one will prefer to use an older version of gimp and a browser than just gimp. Anyway, I am rasing the severity because it is supposed to be critical. After all freetype causes mozilla to crash and that is pretty critical.
Well, I disagree. The proper fix is to use X.org 6.8 in combination with Freetype >2.1.5. GIMP 2.0+ and Freetype 2.1.5+ should be blocked by X.org 6.7.
xorg 6.8 is great and so is freetype > 2.1.5 (especially with the improvements in the rendering engine) however the ati drivers still do not work on xorg above 6.7 and therefore that is not really a solutino. ATI video cards are pretty large chunk of the boards out there so you can't just leave them out.
it also breaks KDE Kcontrol font-installer! http://www.freetype.org/pipermail/freetype/2004-September/007324.html
None of the problems exist in 2.1.7 but it is not in portage. If it was then the problem with gimp 2.2.x will go away. It's probably not the best solution but it's a temporary one. I don't know if 2.1.7 works with KDE and I don't use KDE so I can't test it.
*** Bug 77907 has been marked as a duplicate of this bug. ***
*** Bug 77905 has been marked as a duplicate of this bug. ***
I get this problem when I try to install mplayerplug-in (which requires gecko-sdk)
Here's a workaround if you want to install gecko-sdk. Add: =media-libs/freetype-2.1.9-r1 to your /etc/portage/package.mask file. If it doesn't exist, make it. Then: emerge freetype net-libs/gecko-sdk -va
masking a package is no solution to the problem. However as someone had mentioned the problem is not with freetype but rather the combination of freetype>= 2.1.7 and xorg 6.7. This should not be a problem anymore since ati-drivers now support xorg 6.8 and there is no reason why you should be runnig xorg 6.7. Xorg 6.8 and above works better and it is no supported under every video driver so I am closing this bug. If you are still having a problem your solution should be to updete your X server.
No, I am running xorg-x11-6.8.1.902 and freetype-2.1.9-r1 and my build of gecko-sdk still fails.
Unfortunately, many ATI users are still using Xorg 6.7 (myself included) because all of ATI's drivers after 3.2.8 suffer a memory leak in Neverwinter Nights. This game (possibly others) is unplayable for me using any driver after 3.2.8, including the new 8.8.25. I know from forums that other ATI users are also using 3.2.8. For now, we're still using Xorg 6.7.
Yes apparently the gecko-sdk still does not include a patch for this issue. However, this bug was concering only the browsers and you should probably start a new bug for it. I can't believe it's been over a month and this is still not fixed. I am reopenning the bug because of this but it probably won't change anything. As far as the NeverWinter problem goes this has nothing to do with freetype2 or gentoo in particular. If you choose to run an old version of any software you shouldn't expect support for it. That's pretty much how all OSS works.
If you use the patch from mozilla it should compile correctly (I'm even using 1.7.5)
X11 herd please advise. I'm leaning toward the idea of comment #6, and I don't think this is a purely mozilla issue. Please take ownership of this if you agree.
How could you get that combination, using either a straight stable or a straight ~arch system? The only clear way I can see is upgrading xorg to 6.8.2 to force a freetype upgrade, then downgrading it all the way to 6.7.0. If you want a solution from our end, it'll be pulling 6.7.0 from the tree. I don't have the time to support weird crap, including the above situation. Binary driver users will just be out of luck until it gets fixed (it may be already in 8.10 for all I know).
As an additional note, 6.7.0 would be getting pulled soon anyway, because it's subject to a security vulnerability.
FYI: https://bugzilla.mozilla.org/show_bug.cgi?id=234035
All these bugs http://bugs.gentoo.org/show_bug.cgi?id=71809 http://bugs.gentoo.org/show_bug.cgi?id=75957 http://bugs.gentoo.org/show_bug.cgi?id=71789 seem to be related with this one. Should they be marked as duplicates? Anyway, now firefox-1.0.1 + freetype-2.1.9-r1 is running stable again(x86_64) without being root. Alas, I cannot tell which packages were involved during the last emerge sync && emerge -aDu world
as part of looking at emerge -u world I couldnt emerge -u mozilla-firefox to 1.0.1 which was blocked by freetype. Unmerging mozilla and updating freetype caused Konqueror to stop working (just got a 'unknown page' message). ie freetype-2.1.9 stops firefox 1.0.1 emerging here In file included from /usr/X11R6/include/X11/Xft/Xft.h:35, from nsDeviceContextGTK.cpp:78: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H" gmake[4]: *** [nsDeviceContextGTK.o] Error 1 gmake[4]: *** Waiting for unfinished jobs.... gmake[4]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.1/work/mozilla/gfx/src/gtk' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.1/work/mozilla/gfx/src' gmake[2]: *** [libs] Error 2 gmake[2]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.1/work/mozilla/gfx' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.1/work/mozilla' make: *** [default] Error 2 !!! ERROR: net-www/mozilla-firefox-1.0.1 failed. !!! Function src_compile, Line 108, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message.
@comment 24 : Either your X is too old or you got stale files around. Your problem is not really related to this bug & is discussed in other bugs (search).
*** Bug 71789 has been marked as a duplicate of this bug. ***
*** Bug 75957 has been marked as a duplicate of this bug. ***
*** Bug 71809 has been marked as a duplicate of this bug. ***
I believe this issue is completely fixed with the combination of the latest mozilla, firefox, xorg-x11 and freetype ebuilds. Please re-open only if you're *certain* you're still seeing this bug with the most recent versions.
