Code change:
Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: to chromium 91.0.4472.164 (current on unstable channel) chromium that some area where there should be text do not render, this also happens in the developer console or at chrome://gpu/ for example. Expected behavior No error in font rendering Screenshots ! or ! Additional informations Works on some pages, like or teams, when directly accessing a meeting. Same behavior observed by a colleague running qutebrowser: ! (this is ) ^. ; ; ;,- ,- ,-"""   ^^ ,-; ; ,- / ;; ,^ / ,^ ,-" - qutebrowser v2.3.0 Git commit: Backend: QtWebEngine 5.15.3, based on Chromium 87.0.4280.144 Qt: 5.15.2 CPython: 3.9.5 PyQt: 5.15.4 sip: 6.1.0.dev2104271705 colorama: no jinja2: 3.0.1 pygments: 2.9.0 yaml: 5.4.1 adblock: 0.5.0 PyQt5.QtWebEngineWidgets: yes PyQt5.QtWebEngine: 5.15.4 PyQt5.QtWebKitWidgets: no 2.8.335 (/nix/store/z5n6n43w80lh2p2pfp694q38chlrmnl0-pdfjs-) sqlite: 3.35.5 QtNetwork SSL: OpenSSL 1.1.1k 25 Mar 2021 Style: QFusionStyle Platform plugin: xcb OpenGL: Intel, 4.6 (Compatibility Profile) Mesa 21.1.5 Platform: Linux-5.10.48-x86_64-with-glibc2.33, 64bit Linux distribution: NixOS 21.11 (Porcupine) (nixos) Frozen: False Imported from /nix/store/42sm4xmn4z74m19q7n70b7bgikd9qcy9-qutebrowser-2.3.0/lib/python3.9/site-packages/qutebrowser Using Python from /nix/store/yqjhkdarf7p74wcha7aypzsb751n7wl2-python3-3.9.5/bin/python3.9 Qt library executable path: /nix/store/i1gvlgf0g8scyc9rqk9gcz0pvwnvy6sp-qtbase-5.15.2/libexec, data path: /nix/store/i1gvlgf0g8scyc9rqk9gcz0pvwnvy6sp-qtbase-5.15.2 yaml attribute: chromium module:
Rolling back to chromium v91.0.4472.114 fixes the problem:
I can confirm this issue. All browsers based on seem to be affected. Qutebrowser definitely is.
I can also confirm it (noticed it a few hours ago) but didn't have time to investigate so far. A good revision is and a bad revision so something between those two revisions must've caused this regression (it's unrelated to Chromium updates). I suspect either or maybe .
I'm personally experiencing this in both qutebrowser and Chromium (but Chromium works with on the command line). From what I can tell, this does seem to be caused by the glibc 2.33 update: Chromium bug tracker issue QtWebEngine bug tracker issue Fix in Chromium (this one got reverted) (in version 94, the current dev channel version) Fedora patches for Chromium and QtWebEngine Arch patches for Chromium and QtWebEngine
(qtwebengine maintainer): Could you look into the fix for QtWebEngine (see )? cc (qutebrowser maintainers) Regarding Chromium: should hopefully fix this regression:

Related discussion:
text: url = "https://github.com/qt/qtwebengine/commit/199ea00a9eea13315a652c62778738629185b059.patch"; sha256 = "1b5k2g1v8913cvsgvp6ja4mcprjlk5vcwqzi0p1qq7b1wyi4f0g2"; }) <ins> # Fix invisible fonts with glibc 2.33: https://github.com/NixOS/nixpkgs/issues/131074 (fetchpatch { url = "https://src.fedoraproject.org/rpms/qt5-qtwebengine/raw/d122c011631137b79455850c363676c655cf9e09/f/qtwebengine-everywhere-src-5.15.5-%231904652.patch"; name = "qtwebengine-everywhere-src-5.15.5-_1904652.patch"; sha256 = "01q7hagq0ysii1jnrh5adm97vdm9cis592xr6im7accyw6hgcn7b"; }) </ins> ] ++ optionals stdenv.isDarwin [ ./qtwebengine-darwin-no-platform-check.patch ./qtwebengine-mac-dont-set-dsymutil-path.patch