9.1.2 Observation - LocalUI.Service

[2800GT]

I'm pretty sure it is one of these  https://www.aliexpress.com/item/1005004199505735.html - 7 inch version, branded as KeDei, and has been "plug and play" up to now

Some more details here https://www.ebay.co.uk/itm/7-Inch-TFT-Ca...3659988539

I also have the 5 inch version of this screen on a Pi2 running Volumio (not tried Moode on that unit yet)
These screens replaced a couple of official 7 inch screen which both had their touchscreen functionality fail within weeks of each other ages ago while I was still using LibreElec

[Tim Curtis]

Here's an update on the "chromium-browser issue".

1. It appears that versions of chromium-browser > 126 cause a "drawing error" to be thrown by XServer on < Pi-4. This prevents the moode knob sliders from showing on a locally attached display.
2. Downgrading to chromium-browser 126 fixes this issue.

After some analysis of the chromium-browser package sets and dependencies for version 126 and the more recent chromium-browser upgrades from Raspberry Pi repos and that ship with moode, it looks like the process for downgrading to 126 is not going to be compatible with our standard Pi-Gen based image builder.

This means that a downgrade to chromium-browser 126 will need to be done via an installable patch script which I'll prolly create for convenience or a manual procedure as described earlier in this Thread.

Moode releases will continue to ship with the latest available version of chromium-browser for Raspberry Pi and hopefully a future version of chromium-browser won't have the drawing issue for < Pi-4.

Also, someone (not me) could post/track an issue to the Raspberry Pi Linux repo https://github.com/raspberrypi/linux/issues?q=is%3Aopen with some details about the issue and the specific xinit error:

"Oct 08 12:18:20 moode2 xinit[11847]: Draw call returned Invalid argument.  Expect corruption."

[2800GT]

I'm happy to have a go at posting the issue to the Pi Linux repo if it is as simple as "I'm running xxxx software on yyyy hardware and seeing this error message, and when I make this change the error goes away"
I had a look to see if any similar issue had been logged and noticed the repo landing page says "Kernel issues only" - will they be interested if this is a chromium browser / Xorg error ?

[Tim Curtis]

I'm happy to have a go at posting the issue to the Pi Linux repo if it is as simple as "I'm running xxxx software on yyyy hardware and seeing this error message, and when I make this change the error goes away"
I had a look to see if any similar issue had been logged and noticed the repo landing page says "Kernel issues only" - will they be interested if this is a chromium browser / Xorg error ?

Right, it might be better to post it in the RPI-Distro repo.
https://github.com/RPi-Distro/chromium/issues

Provide platform details. 
They are at the top of the moode SSH login header for example:

Code:

RPiOS: 12.7 Bookworm 64-bit | Linux: 6.6.51 64-bit
Model: Pi-5B 4GB

List the chromium versions and package sets 

# Current package set (dpkg -l | grep chromium)

Code:

hi  chromium                             1:129.0.6668.100-1~deb12u1+rpt1        arm64        web browser
hi  chromium-browser                     1:129.0.6668.100-1~deb12u1+rpt1        all          transitional dummy package
hi  chromium-common                      1:129.0.6668.100-1~deb12u1+rpt1        arm64        web browser - common resources used by the chromium packages
hi  chromium-sandbox                     1:129.0.6668.100-1~deb12u1+rpt1        arm64        web browser - setuid security sandbox for chromium
hi  rpi-chromium-mods                    20240904                               arm64        Raspberry Pi-specific mods to Chromium

# Downgrade package set

Code:

hi  chromium-browser                     126.0.6478.164-rpt1                    arm64        Chromium web browser, open-source version of Chrome
hi  chromium-browser-l10n                126.0.6478.164-rpt1                    all          chromium-browser language packages
hi  chromium-codecs-ffmpeg-extra         126.0.6478.164-rpt1                    arm64        Extra ffmpeg codecs for the Chromium Browser

Provide the downgrade process

Code:

sudo apt update && apt list --upgradable
sudo apt-mark unhold chromium chromium-browser chromium-common chromium-sandbox rpi-chromium-mods
sudo apt -y install chromium-browser=126.0.6478.164-rpt1 chromium-browser-l10n=126.0.6478.164-rpt1 chromium-codecs-ffmpeg-extra=126.0.6478.164-rpt1 --allow-downgrades --allow-change-held-packages
sudo apt -y purge chromium chromium-common chromium-sandbox rpi-chromium-mods
sudo apt -y autoremove
sudo reboot

List xserver version

Code:

pi@moode9:~ $ dpkg -l | grep xserver
ii  x11-xserver-utils                    7.7+9+b1                               arm64        X server utilities
ii  xserver-common                       2:21.1.7-3+rpt3+deb12u7                all          common files used by various X servers
ii  xserver-xorg                         1:7.7+23                               arm64        X.Org X server
ii  xserver-xorg-core                    2:21.1.7-3+rpt3+deb12u7                arm64        Xorg X server - core server
ii  xserver-xorg-input-all               1:7.7+23                               arm64        X.Org X server -- input driver metapackage
ii  xserver-xorg-input-libinput          1.2.1-1+b1                             arm64        X.Org X server -- libinput input driver
ii  xserver-xorg-input-wacom             1.1.0-1                                arm64        X.Org X server -- Wacom input driver
ii  xserver-xorg-legacy                  2:21.1.7-3+rpt3+deb12u7                arm64        setuid root Xorg server wrapper
ii  xserver-xorg-video-all               1:7.7+23                               arm64        X.Org X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu            23.0.0-1                               arm64        X.Org X server -- AMDGPU display driver
ii  xserver-xorg-video-ati               1:19.1.0-3                             arm64        X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev             1:0.5.0-2                              arm64        X.Org X server -- fbdev display driver
ii  xserver-xorg-video-nouveau           1:1.0.17-2                             arm64        X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-radeon            1:19.1.0-3                             arm64        X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa              1:2.5.0-1+b1                           arm64        X.Org X server -- VESA display driver

[2800GT]

Done
https://github.com/RPi-Distro/chromium/issues/50
Hopefully it makes enough sense

[Tim Curtis]

Done
https://github.com/RPi-Distro/chromium/issues/50
Hopefully it makes enough sense

Looks ok to me.

[Tim Curtis]

I didn't realize that --disable-gpu also fixes the issue. I'll do some testing on my end and if there's no perf hit or other issues I'll go with that approach for < pi4 rather than a chromium downgrade option.

[2800GT]

No noticeable performance impact on my machine. As Kent mentioned, disabling GPU removes the "tearing / flickering" that was sometimes seen with it enabled
I guess a performance hit might be more noticeable if video playing or 3D rendering was involved, but very little impact when loading a simple web page.

[FredM]

Well, I suspected my rpi 3b, and bought an 4b version. I can restore the rpii 3 then or use it for another project. I find the performance of the rpi 4 with moode latest version a bit unresponsive. The chromium browser uses a lot of cpu at some moments. I can try the --disable-gpu trick or install the older version.

[Tim Curtis]

Well, I suspected my rpi 3b, and bought an 4b version. I can restore the rpii 3 then or use it for another project. I find the performance of the rpi 4 with moode latest version a bit unresponsive. The chromium browser uses a lot of cpu at some moments. I can try the --disable-gpu trick or install the older version.

Set Prefs > PLAYBACK > Now-playing icon to Waveform.
The animated EQ icon causes chromium to use a lot of CPU