Bug #1479
[iceweasel][icecat][icedove] Garbled text after update of FreeType 2.8.1, if RGB sub-pixel rendering of fonts enabled
100%
Description
Steps to reproduce:
1. Make sure the following is set in ~/.Xresources (I needed to relogin for the changes to come into effect) :
Xft.rgba: rgb
2. Run Iceweasel and open any web-page with text, for example https://www.parabola.nu/
Expected:
Everything is displayed correctly.
Actual:
The text is garbled everywhere in the window. See the attached screenshot.
NOTES:
1. This is observed on KDE Plasma. Haven't been tested on any other DE.
2. Not reproducible if ~/.Xresources is removed. But in this case the font rendering is gray-scale instead of RGB.
3. See news from https://www.freetype.org/ about Harmony, this is a probable cause of the issue.
4. It seems Arch has already patched their firefox package, but I haven't tested it. See https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/firefox for recent changes.
Files
History
Updated by nRoof over 6 years ago
The issue is also reproducible for icecat and icedove packages. Not sure if there are any other Gecko-based packages, but it seems they should be affected too.
Please update the summary of the bug to mentijon additional packages, since it seems this functionality isn't available for me.
Updated by isacdaavid over 6 years ago
- Subject changed from [iceweasel] Garbled text after update of FreeType 2.8.1, if RGB sub-pixel rendering of fonts enabled to [iceweasel][icecat][icedove] Garbled text after update of FreeType 2.8.1, if RGB sub-pixel rendering of fonts enabled
Updated by remi over 6 years ago
Also the case on icecat here on BSPWM. Removing Xft.rgba from the .Xresources didn't help for me. Downgrading freetype2 to freetype2-2.8-2-x86_64 works as a temporary solution.
Updated by oaken-source over 6 years ago
- % Done changed from 0 to 100
- Assignee set to oaken-source
- Status changed from open to fixed
I believe this has been fixed already. If not, please let me know.
Updated by nRoof over 6 years ago
I can confirm that iceweasel and icedove are fixed now. Icecat still has this issue.
Updated by oaken-source over 6 years ago
- % Done changed from 100 to 60
- Status changed from fixed to in progress
Updated by nRoof over 6 years ago
- File Screenshot_20171015_203338.png Screenshot_20171015_203338.png added
- File Screenshot_20171015_202050.png Screenshot_20171015_202050.png added
I just found one more package with the same issue: iceape. Please see attached screenshots for icecat and iceape. Should I log it as a separate bug?
Nothing more found so far from Mozilla family. Checked xulrunner, works fine.
Updated by oaken-source over 6 years ago
I have to admit I can't reproduce the issue :(
However, I ported the patches used to fix the issue in iceweasel to icecat, and it looks like that should do the trick.
I'll look at iceape separately, but I don't think it's a critical issue there.
Updated by ovruni over 6 years ago
- % Done changed from 60 to 100
- Status changed from in progress to fixed