[snap] 66.0.3359.170 in candidate channel renders fonts incorrectly

Bug #1771385 reported by Olivier Tilloy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
High
Olivier Tilloy

Bug Description

Steps to reproduce:

 1) $ snap install chromium
 2) $ snap run chromium
 3) observe that fonts are correctly rendered, both in the chrome and in web content
 4) $ snap refresh chromium --candidate
 5) $ snap run chromium

Expected result: fonts are still rendered correctly.

Current result: fonts are rendered incorrectly (see attached screenshot).

Tags: snap
Revision history for this message
Olivier Tilloy (osomon) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

Revision 307 (the previous build of 66.0.3359.170 for amd64) is also affected.
Revision 302 (the build immediately before 307 of 66.0.3359.170 for amd64) is *not* affected.

Upon inspecting the differences between the contents of those two snaps, it appears that https://github.com/ubuntu/snapcraft-desktop-helpers/commit/f07d125e3ba4d1175ab8f4615e453a933e2fffa7 is what caused the regression.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Copying /snap/chromium/current/etc/fonts/fonts.conf over to ~/snap/chromium/current/.config/fontconfig/ "fixes" the issue, so the contents of fonts.conf generated by the desktop helpers are to blame.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Adding the following line to the generated fonts.conf appears to fix the issue:

    <include ignore_missing="yes">conf.d</include>

Revision history for this message
Olivier Tilloy (osomon) wrote :
Changed in chromium-browser (Ubuntu):
status: New → In Progress
importance: Undecided → High
Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Ads20000 (ads20000) wrote :

Fixed in 66.0.3359.181 (319) [candidate]

Changed in chromium-browser (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.