Bug 19263

Summary: subpixel rendering not working in gtk based applications
Product: Mageia Reporter: Giuseppe Ghibò <ghibomgx>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: eatdirt, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: gtk+3.0-3.20.9-1.mga6.src.rpm, fontconfig?, cairo?, freetype2 CVE:
Status comment:

Description Giuseppe Ghibò 2016-08-29 15:19:26 CEST 
When the subpixel rendering is enabled (this can be enabled in both the KDE configuration->Font, $HOME/.fonts.conf as well as with gnome-tweak-tool), any GTK based application seems to ignore it, and produce only grey-scaled antialiased fonts.

This happens in firefox, chromium-browser, libreoffice, etc.; to reproduce just first enable subpixel rendering through the places above, then run the magnify glass (e.g. through the "xmag" application) and see that in any portion of the window where there are font characters, the antiliasing is realized trough gray-scale colored pixels, instead of red and blue gradient of pixels.

Note also that this happens using both the standard libfreetype6 as well as the version from tainted media source.

The same doesn't happens on QT based applications (e.g. konqueror).

I'm not sure whether this bug belongs to gtk+, but this is the lowest common denominator I found.
Thierry Vignaud 2016-08-29 16:55:13 CEST

Source RPM: gtk+3.0-3.20.9-1.mga6.src.rpm => gtk+3.0-3.20.9-1.mga6.src.rpm, fontconfig?, cairo?

Comment 1 Giuseppe Ghibò 2016-08-29 18:55:05 CEST 
Sound the problem was in freetype2: the path for the include file ftoption.h in SPEC file has changed through releases, so it was no longer matching the version in the tar archive. I fixed in freetype2-2.6.5-2.mga6; in this way it works as it's used to be. IMHO there are still some minor problem of overriding of configurations between gtk-based and qt-based applications (and problably upstream), as well as global configuration and user configuration, but this would require a long taxonomy classification, that IMHO it's worthwhile to do only when freetype 2.7 will be out.

Source RPM: gtk+3.0-3.20.9-1.mga6.src.rpm, fontconfig?, cairo? => gtk+3.0-3.20.9-1.mga6.src.rpm, fontconfig?, cairo?, freetype2

Comment 2 Marja Van Waes 2016-08-31 11:52:48 CEST 
(In reply to Giuseppe Ghibò from comment #1)
> Sound the problem was in freetype2: the path for the include file ftoption.h
> in SPEC file has changed through releases, so it was no longer matching the
> version in the tar archive. I fixed in freetype2-2.6.5-2.mga6; in this way
> it works as it's used to be. IMHO there are still some minor problem of
> overriding of configurations between gtk-based and qt-based applications
> (and problably upstream), as well as global configuration and user
> configuration, but this would require a long taxonomy classification, that
> IMHO it's worthwhile to do only when freetype 2.7 will be out.

CC'ing eatdirt, because of a maybe wrong memory that he hit this bug, too

CC: (none) => eatdirt, marja11

Comment 3 Marja Van Waes 2016-09-01 12:20:51 CEST 
Anyway, closing as fixed because freetype2-2.6.5-2.mga6 and freetype2-2.6.5-2.mga6.tainted were already pushed.

Thanks joeghi :-)

Status: NEW => RESOLVED
Resolution: (none) => FIXED