Okay. That experimental.refresh-app-awareness did not fix it.
This morning (16 March), while switching tabs, the font "change"
occurred visibly again. Apparently I'm not looking at a fresh Chromium.
Yet still there is _something_ that messed up the fonts.
Here's some system info:
$ snap list --all chromium
Name Version Rev Tracking Publisher Notes
chromium 98.0.4758.9 1868 latest/stable canonical✓ disabled
chromium 96.0.4664.110 1854 latest/stable canonical✓ disabled
chromium 98.0.4758.54 1873 latest/stable canonical✓ disabled
chromium 97.0.4692.99 1878 latest/stable canonical✓ disabled
chromium 98.0.4758.80 1895 latest/stable canonical✓ disabled
chromium 98.0.4758.80 1899 latest/stable canonical✓ disabled
chromium 98.0.4758.102 1912 latest/stable canonical✓ disabled
chromium 99.0.4844.51 1926 latest/stable canonical✓ -
Running processes and start-time:
$ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e
's/,$//') | awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c
1 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome
--password-store
3 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome --type=zygote
1 Mar 7 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--password-store
3 Mar 7 /snap/chromium/1926/usr/lib/chromium-browser/chrome --type=zygote
1 Mar 7 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=gpu-process
2 Mar 7 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=utility
4 Mar 7 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
1 Mar 8 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=utility
1 Mar 8 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
1 Mar 9 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
1 Mar 14 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
34 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
1 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=utility
2 Mar 15 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
So, apparently there _are_ two chromiums running at the same time. Not
sure why, but that might explain conflicts. The old one was branched off
a --password-store parent.
Looking at the age in the fontconfig dir:
$ ls /var/snap/chromium/common/fontconfig/ -ltr
total 1700
-rw-r--r-- 1 root root 151 mrt 2 15:39 fonts.conf
-rw-r--r-- 1 root root 408 mrt 2 15:39
34e0e5ac-5c62-4453-a219-f92185a510d1-le64.cache-7
...
-rw-r--r-- 1 root root 104 mrt 2 15:39
34e3ea57-0766-47d7-ac34-3152aff3ab1c-le64.cache-7
-rw-r--r-- 1 root root 152 mrt 2 15:39
2bdf00a0-773f-43e6-bc52-f8023b64a749-le64.cache-7
So, all files are from the same date and not recently changed or
something.
Steps I did now:
- $ sudo rm /var/snap/chromium/common/fontconfig/*
- fonts were still bad
- stopping chromium (alt-4)
- observe how the old chromium is still running:
$ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e 's/,$//')
| awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c
1 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome
--password-store
3 Feb 11 /snap/chromium/1899/usr/lib/chromium-browser/chrome --type=zygote
- start chromium again
- fonts are good again
I'm killing off the old chromium/1899 now:
$ kill 965195 965392 965393 965395
(Where the parent 965195 refuses to die without SIGKILL.)
Restarted chromium again, for good measure.
$ ps -ho lstart,command -p $(pgrep -f chromium | tr '\n' , | sed -e 's/,$//')
| awk '{print $2 " " $3 " " $6 " " $7}' | uniq -c
1 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--password-store
3 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome --type=zygote
1 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=gpu-process
2 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=utility
9 Mar 16 /snap/chromium/1926/usr/lib/chromium-browser/chrome
--type=renderer
Observe that the fontconfig directory is empty at this point (even
though chromium has started twice after purging it).
Now wait for the issue to reappear...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1954980
Title:
[snap] Chromium showing Japanese fonts incorrectly
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
It simply shows square rectangles for all Japanese characters this
occurred after a recent update (earlier this week), a restart fixed it
the first time but now it has reverted, probably after another update.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 16 11:54:12 2021
InstallationDate: Installed on 2019-02-08 (1041 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
Snap: chromium 96.0.4664.110 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
