Kiosk mode quits once in a while

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | 9.12.1
  • Distro version | bookworm 0
  • Kernel version | 6.12.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.20-1+rpt1~bpo12+1 (2025-03-19) aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi3 Model B
  • Power supply used | 5V 2.5A official power supply
  • SD card used | (EG: SanDisk ultra)

Additional Information (if applicable)

  • Software title | Chromium Kiosk mode
  • Was the software title installed freshly or updated/migrated?: Was running for probably several years, problems started with one of the latest upgrades
  • Can this issue be replicated on a fresh installation of DietPi? I do not know

Steps to reproduce

  1. having kiosk mode running on a above system, let’s say from February 2025
  2. Run upgrades (which were including x-server and probably chromium)

Expected behaviour

  • It should work as I did long time before

Actual behaviour

I am not sure why the xserver terminated. If more logging is needed, please let me know, where it is located.

I have two system running, one with the display connected via HDMI, one with the display connected via DSI. Both started the issue at the same time.

Thanks in advance!
BR,
Bernhard

2

maybe not the same issue but some of the error messages looks similar Chromium won't run in headless mode on NanoPi Neo3 (headless SBC) · Issue #7489 · MichaIng/DietPi · GitHub

You could try

apt install dbus-x11 upower
systemctl start upower
3

Same here.. almost the same system.. Rpi 3b with a small HDMI 7" screen… from what I can tell it started when chromium last updated… about a week ago? same screen errors i got.. Also.. tried it on a Orange Pi Zero 3 same thing after an hour or so… the webpage being display is a Home Assistant Dashboard. (note: in my errors it mentions the GPU being unsupported… )

4

from what I can tell it started when chromium last updated… about a week ago?

I unfortunately do not remember exactly, when it started. But definitely it could be related to the last chromium update also at my Rpis!

You could try

apt install dbus-x11 upower
systemctl start upower

dbus-x11 was already installed and latest version. upower I installed now. I will try!

Thanks for the inputs!

Bernhard