Fixed in 66.0.3359.181 (319) [candidate]
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771385
Title:
[snap]
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771385
Title:
[snap] 66.0.3359.170 in candidate channel renders
This PR should fix the issue: https://github.com/ubuntu/snapcraft-
desktop-helpers/pull/116
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are
Adding the following line to the generated fonts.conf appears to fix the
issue:
conf.d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771385
Title:
[snap] 66.0.3359.170 in candidate channel
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
