Bug 1816442

Summary: webkit2gtk3-2.28 breaks font antialiasing
Product: [Fedora] Fedora Reporter: Radu Rendec <radu>
Component: webkit2gtk3Assignee: Michael Catanzaro <mcatanza>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 30CC: erack, gnome-sig, mcatanza, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-24 13:24:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Evolution screenshot using webkit2gtk3-2.28
none
Evolution screenshot using webkit2gtk3-2.24 none

Description Radu Rendec 2020-03-24 01:05:01 UTC
Created attachment 1672873 [details]
Evolution screenshot using webkit2gtk3-2.28

Description of problem:

After upgrading to the latest version of webkit2gtk3 from F30, font antialiasing is broken in Evolution email rendering.

Version-Release number of selected component (if applicable):

webkit2gtk3-2.28.0-5.fc30.x86_64

How reproducible:

Always. Upgrade to the latest version of the package.

Additional info:

Downgrading *only* webkit2gtk3 (and the webkit2gtk3-jsc subpackage) solves the problem. Upgrading the package makes the problem appear again.

I have attached screenshots of the same Evolution window with the new (broken) version of webkit2gtk3 and the old (working) version of webkit2gtk.

Comment 1 Radu Rendec 2020-03-24 01:06:02 UTC
Created attachment 1672874 [details]
Evolution screenshot using webkit2gtk3-2.24

Comment 2 Michael Catanzaro 2020-03-24 13:24:44 UTC
We're not going to solve this downstream. You can report on WebKit Bugzilla, WebKitGTK component. Prefix the title of your bug with [FreeType].

That said: it's strange that nobody else has reported seeing this issue.

Comment 3 Michael Catanzaro 2020-03-24 19:52:19 UTC
Oh it's your lucky day, I just found https://trac.webkit.org/changeset/255865/webkit.

I'll ask for this to be backported to 2.28.1. In the meantime, you can move your ~/.fontconfig directory to ~/.config/fontconfig, which is a better place anyway.

Comment 4 Michael Catanzaro 2020-03-24 19:53:42 UTC
Sorry, I'm wrong, that commit is already included.

I'm pretty sure your problem is similar, though. Maybe you could try figuring out where you have stored custom font configuration. Then you can open an upstream bug requesting the sandbox be updated.

Comment 5 Radu Rendec 2020-03-24 20:10:01 UTC
My font configuration is already in ~/.config/fontconfig/fonts.conf - but you're right, my problem is likely similar.

At least now I have an idea where to look and were to ask for help in case I need it. Thank you so much for the information! I appreciate it.

Comment 6 Michael Catanzaro 2020-07-13 17:29:45 UTC
We figured out that access to font settings inside the sandbox depends on both gnome-settings-daemon and xdg-desktop-portal-gtk. You don't need gnome-settings-daemon running, it just has to be installed because that's where the font settings live. See https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/31