| Summary: | GTK apps don't respect global/user lcdfilter font settings without a sub-pixel rendering enabled freetype2 build | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Hrvoje Senjan <hrvoje.senjan> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, hrvoje.senjan, pavel.penchev |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | http://imageshack.us/f/835/screennc.png/ | ||
| Whiteboard: | |||
| Source RPM: | freetype2 | CVE: | |
| Status comment: | |||
| Bug Depends on: | 1909 | ||
| Bug Blocks: | |||
|
Description
Hrvoje Senjan
2011-06-03 12:49:59 CEST
Hrvoje Senjan
2011-06-03 12:50:11 CEST
CC:
(none) =>
hrvoje.senjan Screenshot #2 , side by side using same fonts: http://imageshack.us/photo/my-images/191/snimka2.png/ As has been said in the forum, you need a freetype2 build where sub-pixel rendering is enabled, this will happen in the freetype2 build that will be pushed to the Tainted repo; the package will be available after the freeze is over and packages can be submitted to the build system again. Leaving the report open until the package is available. Summary:
GTK apps don't respect global/user font settings =>
GTK apps don't respect global/user lcdfilter font settings without a sub-pixel rendering enabled freetype2 build Do you have a rough idea when the freetype2+subpixel rendering will hit the Tainted repo? I depend on some GTK apps (Eclipse/Firefox) but I'd like to skip compiling the stuff myself. CC:
(none) =>
pavel.penchev I see you're running x86_64; these packages are built by me locally (in a clean chroot) for my own usage, you can use them if you like until the release freeze is over and packages can be submitted to the build system: http://ryu.zarb.org/~ahmad/lib64freetype6-2.4.4-4.1.mga1.x86_64.rpm http://ryu.zarb.org/~ahmad/lib64freetype6-devel-2.4.4-4.1.mga1.x86_64.rpm http://ryu.zarb.org/~ahmad/lib64freetype6-static-devel-2.4.4-4.1.mga1.x86_64.rpm I will try it , thanks :) Ahmad , your package fixed the issue :). Thank you
Ahmad Samir
2011-06-24 10:41:21 CEST
Depends on:
(none) =>
1909 I've installed freetype2-demos from the Tainted Updates Testing repository, which correctly pulled in the dependencies. I tested the installation using ftview 72 /usr/share/fonts/TTF/dejavu/DejaVuSans.ttf I think that's sufficient qa testing for the i586 version. If someone with a 64 bit install can repeat the test in that version, the packages can then be moved to Tainted Updates. CC:
(none) =>
davidwhodgins I noticed that building the tainted version also creates Core Updates Testing versions, so I've tested those with rpm -e --nodeps libfreetype6-static-devel libfreetype6-devel libfreetype6 freetype2-demos urpmi --media "Core Updates Testing" freetype2-demos ftview 72 /usr/share/fonts/TTF/dejavu/DejaVuSans.ttf The i586 version of the packages ... libfreetype6-static-devel libfreetype6-devel freetype2-demos libfreetype6 are ready to be pushed to Core Updates The update request is in bug 1099, everything goes there after its creation, to keep everything in one place. It's bug 1909. Right. It's correct in the dependency field Status:
NEW =>
RESOLVED |