9.1.2 Observation - LocalUI.Service

[2800GT]

This post was going to be a request for help but I seem to have fixed my problem. Still I thought it was worth sharing.

I am running Moode on a PI 3B with IQaudio DAC and DSI LCD touchscreen
When I performed the "In place update" to 9.1.2 (from 9.1.0 I think) I lost my local display (LocalUI.Service failed)
I did a clean, new build using the 9.1.2 download and everything seemed to be working until first reboot when I again lost LocalUI.Service
I then did a clean, new build of my old 9.0.8 download and everything worked normally for several days (multiple reboots, all good)
So I decided to re-try the in place update to 9.1.2 having checked the forum to see if anyone else had similar issues
Again I lost LocalUI.Service as soon as I did the first reboot.

While browsing the System settings I spotted something called Log to RAM which looked to be a new feature in 9.1.2 and it was enabled.
I turned it off and suddenly I have my local display back !

I've rebooted and everything is still working as normal - haven't tried turing Log to RAM back on as I don't want to jinx it.

I guess this is not a widespread problem as there would be some mention on the forum but thought it worth mentioning.

Cheers,
Graham

[2800GT]

This post was going to be a request for help but I seem to have fixed my problem. Still I thought it was worth sharing.

I am running Moode on a PI 3B with IQaudio DAC and DSI LCD touchscreen
When I performed the "In place update" to 9.1.2 (from 9.1.0 I think) I lost my local display (LocalUI.Service failed)
I did a clean, new build using the 9.1.2 download and everything seemed to be working until first reboot when I again lost LocalUI.Service
I then did a clean, new build of my old 9.0.8 download and everything worked normally for several days (multiple reboots, all good)
So I decided to re-try the in place update to 9.1.2 having checked the forum to see if anyone else had similar issues
Again I lost LocalUI.Service as soon as I did the first reboot.

While browsing the System settings I spotted something called Log to RAM which looked to be a new feature in 9.1.2 and it was enabled.
I turned it off and suddenly I have my local display back !

I've rebooted and everything is still working as normal - haven't tried turing Log to RAM back on as I don't want to jinx it.

I guess this is not a widespread problem as there would be some mention on the forum but thought it worth mentioning.

Cheers,
Graham

Update - the local display is now showing but it looks like there are still some errors.
It doesn't seem to be drawing the "track progress" and "volume" circles 

Code:

pi@moode2:~ $ systemctl status localui.service
● localui.service - Start Chromium Browser
    Loaded: loaded (/lib/systemd/system/localui.service; disabled; preset: enabled)
    Active: active (running) since Tue 2024-10-08 12:18:10 BST; 3min 20s ago
  Main PID: 11769 (xinit)
     Tasks: 80 (limit: 775)
       CPU: 2min 5.019s
    CGroup: /system.slice/localui.service
            ├─11769 /usr/bin/xinit -- -nocursor
            ├─11770 /usr/lib/xorg/Xorg :0 -nocursor
            ├─11776 /bin/bash /home/pi/.xinitrc
            ├─11787 /usr/lib/chromium/chromium --force-renderer-accessibility --enable-remote-extensions --show-component-extension-options --enable-gpu-rasterization --no-default-browser-check --disable-pings --media-router=0 --enable-remote-extensions --load-extension>
            ├─11804 /usr/lib/chromium/chrome_crashpad_handler --monitor-self --monitor-self-annotation=ptype=crashpad-handler "--database=/home/pi/.config/chromium/Crash Reports" "--annotation=channel=built on Debian GNU/Linux 12 (bookworm)" "--annotation=lsb-release=De>
            ├─11807 /usr/lib/chromium/chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=crashpad-handler "--database=/home/pi/.config/chromium/Crash Reports" "--annotation=channel=built on Debian GNU/Linux 12 (bookworm)" "--annotation=lsb-relea>
            ├─11810 "/usr/lib/chromium/chromium --type=zygote --no-zygote-sandbox --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --change-stack-guard-on-fork=enable"
            ├─11811 "/usr/lib/chromium/chromium --type=zygote --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --change-stack-guard-on-fork=enable"
            ├─11823 "/usr/lib/chromium/chromium --type=zygote --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --change-stack-guard-on-fork=enable"
            ├─11847 "/usr/lib/chromium/chromium --type=gpu-process --enable-gpu-rasterization --ozone-platform=x11 --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --change-stack-guard-on-fork=enable --gpu-pr>
            ├─11849 "/usr/lib/chromium/chromium --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --chang>
            ├─11850 "/usr/lib/chromium/chromium --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --ch>
            ├─11876 "/usr/lib/chromium/chromium --type=renderer --string-annotations --crashpad-handler-pid=0 --enable-crash-reporter=,built on Debian GNU/Linux 12 (bookworm) --change-stack-guard-on-fork=enable --ozone-platform=x11 --lang=en-US --num-raster-threads=2 -->
            └─11895 "/usr/lib/chromium/chromium --type=broker"

Oct 08 12:18:17 moode2 xinit[11787]: [11787:11787:1008/121817.421426:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11828:1008/121817.422073:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11787:1008/121817.443584:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11839:1008/121817.445153:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11787:1008/121817.456581:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11842:1008/121817.457353:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Oct 08 12:18:17 moode2 xinit[11787]: [11787:11787:1008/121817.459854:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
Oct 08 12:18:18 moode2 xinit[11847]: [11847:11906:1008/121818.298830:ERROR:v4l2_utils.cc(572)] Could not open /dev/video10: Permission denied (13)
Oct 08 12:18:18 moode2 xinit[11847]: [11847:11906:1008/121818.300565:ERROR:v4l2_utils.cc(572)] Could not open /dev/video10: Permission denied (13)
Oct 08 12:18:20 moode2 xinit[11847]: Draw call returned Invalid argument.  Expect corruption.

[TheOldPresbyope]

@2800GT 

The only moOde player I have with a local display (official RPi 7" touchscreen) is still running r9.1.0. I'll update it to r9.1.2 and see what I can see.

As an aside, xinit has been throwing "Failed to connect" messages for a long time. I, for one, have never taken the time to try to understand what it was trying to do (DBus is a bit of a blackbox for me).

Regards,
Kent

[TheOldPresbyope]

I have to get ready to go to a meeting* so could only do a quick check of the basics.

r9.1.2 with logtoRAM enabled: the local display can't start because the Xserver isn't running. Check the log

Code:

Oct 08 08:49:26 mpi3bplcd xinit[1711]: Fatal server error:
Oct 08 08:49:26 mpi3bplcd xinit[1711]: (EE) no screens found(EE)

r9.1.2 with logtoRAM disabled: the local display starts but has various breakage.

Lots to investigate. Not only is the logtoRAM function new but the update bumped everything from the kernal to the chromium-browser.

Regards,
Kent

*I've been retired for donkey's years but couldn't resist joining our local community's technology committee

[2800GT]

Thanks for looking into this

I think you are right that there were some random xinit error message while everything was working (mostly "/org/freedesktop/DBus" related) but I think the errors on the end of the dump may be new e.g. "Could not open /dev/video10: Permission denied" and "Draw call returned Invalid argument. Expect corruption"
Am I right in thinking the failed "Draw call" may be why my local display is missing the track time and volume circles

Update - only the "Draw call returned Invalid argument. Expect corruption" is new. The video10 error was there at 9.0.8 and the local display worked fine.

[Tim Curtis]

I ran some quick tests with a fresh 9.1.2 image (kernel 6.6.47) and did not experience any local display issues with Pi4 or Pi5 however there appears to be display breakage with Pi3. Missing knob sliders, partial backgrounds, etc. This occurs on Pi 7" Touch and local HDMI display.

I get same results with the WIP 9.1.3 image that has kernel bump to 6.6.51 and other updated RaspiOS packages.

I won't be able test again until later in the week but if someone could try a Pi3 or 3B+ with an earlier image for example 9.0.8 (kernel 6.6.31) and see if the display issues are still present.

[TheOldPresbyope]

I should have said. My touchscreen is packaged together with a Pi 3B+ and I updated it from r9.1.0.

I’ll have time later today to dig in.

Regards,
Kent

[2800GT]

Tim, when you say "if someone could try a Pi3 or 3B+ with an earlier image for example 9.0.8" do you mean someone other than me ?

If it helps I can re-try 9.0.8 and 9.1.0 looking specifically for local display problems

[TheOldPresbyope]

My Pi 3B+ with touchscreen lash up has worked well with previous releases except for an odd tearing of the screen display when I go from normal moOde screens to configure screens. There were some inscrutable journal entries as I mentioned but the localUI soldiered on.

Regards,
Kent

[Tim Curtis]

Tim, when you say "if someone could try a Pi3 or 3B+ with an earlier image for example 9.0.8" do you mean someone other than me ?

If it helps I can re-try 9.0.8 and 9.1.0 looking specifically for local display problems

I meant anyone :-) 

Please give it a try, thx.