Hi everyone,
I've followed the exact instructions from this thread to install Raspberry Pi OS Lite + GNOME (64-bit) on my Raspberry Pi 5.
After a recent system update (April 7th), both YouTube and Netflix in Chromium started showing a white screen for video, while audio still plays normally.
I haven't tested other apps or media players — this issue only occurs in Chromium, with YouTube and Netflix.
This issue does not occur on the official Raspberry Pi OS Desktop build — only with this Lite + GNOME 64-bit setup.
I suspect it began after Chromium was updated to version 134.0.6998.117, but since other packages were also upgraded at the same time, I’m including the full upgrade list for reference:
Would appreciate if anyone else using GNOME 64-bit on a Pi 5 could confirm this behavior — or suggest a fix or workaround.
Thanks!
I've followed the exact instructions from this thread to install Raspberry Pi OS Lite + GNOME (64-bit) on my Raspberry Pi 5.
After a recent system update (April 7th), both YouTube and Netflix in Chromium started showing a white screen for video, while audio still plays normally.
I haven't tested other apps or media players — this issue only occurs in Chromium, with YouTube and Netflix.
This issue does not occur on the official Raspberry Pi OS Desktop build — only with this Lite + GNOME 64-bit setup.
I suspect it began after Chromium was updated to version 134.0.6998.117, but since other packages were also upgraded at the same time, I’m including the full upgrade list for reference:
Code:
wobbo@wobbo-d5:~ $ grep " upgrade " /var/log/dpkg.log2025-04-03 16:32:08 upgrade signal-desktop-unofficial:arm64 7.48.0 7.49.02025-04-04 18:34:35 upgrade signal-desktop-unofficial:arm64 7.49.0 7.48.02025-04-04 19:24:29 upgrade signal-desktop-unofficial:arm64 7.48.0 7.49.02025-04-05 22:55:58 upgrade liblzma5:arm64 5.4.1-0.2 5.4.1-12025-04-05 22:55:59 upgrade xz-utils:arm64 5.4.1-0.2 5.4.1-12025-04-05 22:55:59 upgrade code:arm64 1.98.2-1741787947 1.99.0-17436314552025-04-07 21:59:58 upgrade libc6-dbg:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 21:59:59 upgrade libc-devtools:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 21:59:59 upgrade libc6-dev:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 21:59:59 upgrade libc-dev-bin:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 21:59:59 upgrade libc6:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 22:00:00 upgrade libc-bin:arm64 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 22:00:02 upgrade libc-l10n:all 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 22:00:02 upgrade locales:all 2.36-9+rpt2+deb12u9 2.36-9+rpt2+deb12u102025-04-07 22:00:02 upgrade chromium-l10n:all 1:130.0.6723.116-1~deb12u1+rpt1 1:134.0.6998.117-1~deb12u1+rpt12025-04-07 22:00:03 upgrade chromium:arm64 1:130.0.6723.116-1~deb12u1+rpt1 1:134.0.6998.117-1~deb12u1+rpt12025-04-07 22:00:05 upgrade chromium-common:arm64 1:130.0.6723.116-1~deb12u1+rpt1 1:134.0.6998.117-1~deb12u1+rpt12025-04-07 22:00:05 upgrade chromium-sandbox:arm64 1:130.0.6723.116-1~deb12u1+rpt1 1:134.0.6998.117-1~deb12u1+rpt12025-04-07 22:00:06 upgrade chromium-browser:all 1:130.0.6723.116-1~deb12u1+rpt1 1:134.0.6998.117-1~deb12u1+rpt12025-04-07 22:00:06 upgrade libnuma1:arm64 2.0.16-1 2.0.18-1~rpt12025-04-07 22:00:06 upgrade xserver-common:all 2:21.1.7-3+rpt3+deb12u8 2:21.1.7-3+rpt3+deb12u92025-04-07 22:00:06 upgrade xserver-xephyr:arm64 2:21.1.7-3+rpt3+deb12u8 2:21.1.7-3+rpt3+deb12u92025-04-07 22:00:06 upgrade xserver-xorg-legacy:arm64 2:21.1.7-3+rpt3+deb12u8 2:21.1.7-3+rpt3+deb12u92025-04-07 22:00:06 upgrade xserver-xorg-core:arm64 2:21.1.7-3+rpt3+deb12u8 2:21.1.7-3+rpt3+deb12u9Would appreciate if anyone else using GNOME 64-bit on a Pi 5 could confirm this behavior — or suggest a fix or workaround.
Thanks!
Statistics: Posted by Wobbo — Tue Apr 08, 2025 12:38 pm