© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Okay. That experimental.
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/
3 Feb 11 /snap/chromium/
1 Mar 7 /snap/chromium/
3 Mar 7 /snap/chromium/
1 Mar 7 /snap/chromium/
2 Mar 7 /snap/chromium/
4 Mar 7 /snap/chromium/
1 Mar 8 /snap/chromium/
1 Mar 8 /snap/chromium/
1 Mar 9 /snap/chromium/
1 Mar 14 /snap/chromium/
34 Mar 15 /snap/chromium/
1 Mar 15 /snap/chromium/
2 Mar 15 /snap/chromium/
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/
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-
...
-rw-r--r-- 1 root root 104 mrt 2 15:39 34e3ea57-
-rw-r--r-- 1 root root 152 mrt 2 15:39 2bdf00a0-
So, all files are from the same date and not recently changed or something.
Steps I did now:
- $ sudo rm /var/snap/
- 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/
3 Feb 11 /snap/chromium/
- 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/
3 Mar 16 /snap/chromium/
1 Mar 16 /snap/chromium/
2 Mar 16 /snap/chromium/
9 Mar 16 /snap/chromium/
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...