10-09-2024, 10:54 AM
Looks like a bug in the 129 build of chromium.
If I apt upgrade a fresh 9.1.0 system with only the chromium packages marked as hold then no display issues.
The remedy should be to go with < 129 build of chromium until testing indicates the bug in 129 or higher has been fixed. The question is what package versions are currently in the Debian archive pool, prolly not 128 yet. I'll do some investigation and post the results later today or tomorrow.
For the log2ram issue try the following to reduce the amount of memory it uses. I see it's currently using a default of 128M and it should be 32M. Prolly a missing config edit in the moode-player package postinstall script.
If I apt upgrade a fresh 9.1.0 system with only the chromium packages marked as hold then no display issues.
Code:
pi@moode910:~ $ dpkg -l | grep chromium
hi chromium 1:128.0.6613.137-1~deb12u1+rpt2 arm64 web browser
hi chromium-browser 1:128.0.6613.137-1~deb12u1+rpt2 all transitional dummy package
hi chromium-common 1:128.0.6613.137-1~deb12u1+rpt2 arm64 web browser - common resources used by the chromium packages
hi chromium-sandbox 1:128.0.6613.137-1~deb12u1+rpt2 arm64 web browser - setuid security sandbox for chromium
ii rpi-chromium-mods 20240904 arm64 Raspberry Pi-specific mods to ChromiumThe remedy should be to go with < 129 build of chromium until testing indicates the bug in 129 or higher has been fixed. The question is what package versions are currently in the Debian archive pool, prolly not 128 yet. I'll do some investigation and post the results later today or tomorrow.
For the log2ram issue try the following to reduce the amount of memory it uses. I see it's currently using a default of 128M and it should be 32M. Prolly a missing config edit in the moode-player package postinstall script.
Code:
# Update log2ram memory size (reduce from default 128M to 32M)
sudo sed -i "s/^SIZE=.*/SIZE=32M/" /etc/log2ram.conf