[PROBLEM] Local display blank

[boomblip]

Hi there,

I have issues with (I'm guessing) httpd not being ready when Chromium is starting, which results in the locally attached display not always loading the webinterface for moode.
On every other restart, perhaps related to having shut off power instead of graceful shutdown(?), then when Moode starts everything is displayed while loading until the Chromium (chromeless) frame (white screen) starts. But then nothing more ever loads. 
On rare occasions it pops up a warning in Chromium about webpage not responding, but not always.
Leaving it alone on the white screen does nothing, just a constant white screen. It will then turn off screen following the rule for that and will ignite the white on play, but no interface on screen.

To resolve it, it is "usually" enough to restart the Local Display through Configure -> Peripherals.
It seems a bit random whether or not it works or not.

Any good ideas how to resolve it and ensure the interface always comes up?

If not the case already, I would suggest that the httpd and webinterface return a health check OK state before starting the Chromium process, but I'm just guessing wildly here ? 

Thanks for chipping in.

P.S. A sidenote is that every now and then I also experience that the peripherals settings will "reset" and forget brightness settings, gpu acceleration boolean, etc. The SD card is new and I've seen these issues across identical hardware and all new sd cards, so I'm 99.9% that it's not SD related.

Setup:
Moode 9.2.6 2025-03-07
Raspberry Pi 5 4GB
Raspberry Touchscreen 1 (with the new cable)
Raspberry DAC+ Hat

Here's what I'm building:

[the_bertrum]

Nice looking cases, I like the colour co-ordinated power supply.

Alas I have no insights to offer on your problem though. Someone will be along in a minute I'm sure.

[Tim Curtis]

The symptoms you list are very unusual. I have a couple of systems with locally attached displays and no issues.

- WebUI does not come up on locally attached display
- Settings on the Peripherals screen are not persistent

Best to reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

[boomblip]

The symptoms you list are very unusual. I have a couple of systems with locally attached displays and no issues.

- WebUI does not come up on locally attached display
- Settings on the Peripherals screen are not persistent

Best to reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from  any of the Config screens. The startup log will be at the end of System info output.

Thank you for the answer Tim. I've looked into moode.log and nothing stands out as erroneous or broken.
I'll try a couple runs with debug logging enabled and see if I can get it to replicate the behaviour and learn more.
Don't have much time the coming days but will get back as time permits.