Font/Character Rendering Issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've been building some single purpose kiosks using Ubuntu server on RaspberyPis (models 3 and 4). It's a minimal build that uses matchbox-
Prior to 22.04 we had no issues (see 'correct font' link). Building new Pi images from a base 22.04 install I'm encountering these font issues.
My process is pretty simple. We use the RaspberryPi Imager to create the base install, then update && upgrade. After that we have some scripts to install our packages and some configurations files to auto login and run our xinit script at the end of .bashrc to open the webpage.
Everything is working fine except for this issue with the font. From what I can tell the specific font in the css of the webpage is not installed, but sans-serif is the fallback in the css code and that appears to be used, but it is just rendering wierd.
Looking for similar issues online I have tried to refresh the font cache but not much else comes up.
I've managed to install chrome (proper) from the debian stable repository and have no issues. This is not an ideal workaround due to other issues that will surely arise.
I am attaching an image with 3 screen clips (2 buggy font renders and 1 correct from an older build that doesn't have this issue).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
ProcVersionSign
Uname: Linux 5.15.0-1029-raspi aarch64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: arm64
CasperMD5CheckR
Date: Thu Jun 1 09:41:58 2023
ImageMediaBuild: 20230217.1
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
Snap: chromium 113.0.5672.126 (latest/stable)
Snap.Changes:
ID Status Spawn Ready Summary
5 Error 2023-05-
7 Done 2023-06-
SnapSource: ubuntu/
UpgradeStatus: No upgrade log present (probably fresh install)
Hi Chris, thanks for the bug report.
The attached file is not actually a PNG (it is identified as "Paint.NET image data") and I cannot open it, could you please upload a new one in a common format?
Could you share address of the affected web site and see if you get something either in the journal, i.e.,
journalctl -f
or in the Chromium log,
chromium --enable- logging= stderr
?