I know, the title sounds both dirty and lame today, but I can’t get anything better right now…
So, ten days ago I got reported a high memory consumption bug in KPDF, where opening some PDF could cause at least up to 700MB of memory being used by the kpdf process, this time unrelated to the Poppler patch, but related instead to the FreeType version: in Gentoo we were still stuck with the 2.1 version, even for ~arch tree. The “new” 2.2 version was under package.mask for more than six months now, and foser isn’t around (as usual?).
Most of the packages in the tree, also, were already fixed for FreeType 2.2, at least I’ve been using it for all this time without having a single failure. The older versions of Qt and KDE that failed with that version of FreeType are now fixed, so that is no more a problem.
As the bug above isn’t exactly something you wish to get on a stable system, I’d be for marking this stable as soon as possible, to the limit of possibilities. So I’d really like if as many users as possible will start testing freetype 2.3.1 on stable systems (which aren’t mission critical of course, as I cannot guarantee it will be totally flawless).
I’ll probably try to do some of the work myself using a chroot on pitr, but I’m currently fighting with some packages for my work, and I’m taking care of already too many things, so please, all help is welcome!
Thanks mate,I upgraded to unstable freetype-2.3.1 but kdm wouldn’t start after a reboot.I had to upgrade to media-libs/fontconfig-2.3.2-r2 to get rid of a seg fault.My system is AMD64 64 bit,Andrew
Uhm, was it a segmentation fault or it didn’t start in general? I think that freetype 2.1 and 2.2 has different sonames (as 2.2 removes the internal symbols) so it should require a rebuild of the linked packages; if you use –as-needed, likely the only thing needed by kdm is fontconfig, that needs to be rebuilt.If it’s a segmentation fault, we’re gonna need a new fontconfig stable too.
From the ChangeLog:*fontconfig-2.3.2-r2 (18 Sep 2006) fontconfig-2.3.2-noftinternals.patch : Don’t break on freetype 2.2 (#140359)Could be more stuff that’s fixed only in ~arch, probably hard to find out what will need to be stabled if there’s no tracker bug 🙁
Hi Diego,It compiles and runs fine here (as far as I can see, I’ll keep using it and will post back if I run across anything).I’m running a Hardened x86 system with Xfce4.4, Xorg-7.1 and using the nv driver.I also have the “Use sub pixel hinting enabled”.
no problems here – fully ~x86 system with mostly c++ development apps, and some multimedia software.using 2.3.1 of course :]