MichaIng
MichaIng
Oh, it seems `dbus` is not installed. I guess you installed the package manually without X11, right? ```sh sudo apt install dbus ``` Furthermore, possibly systemd PAM support might be...
Ah right, otherwise `/etc/chromium.d/dietpi` wouldn't be there. No point to uninstall Chromium. Calling it with `--headless` already fixes the "missing X11" error, so that works all as intended. The "Requested...
Hmm, there might be some variables missing when skipping the X11 session. Can you try these steps: https://github.com/microsoft/WSL/issues/7915#issuecomment-2466607845 ```sh export XDG_RUNTIME_DIR=/run/user/$(id -u) sudo mkdir "$XDG_RUNTIME_DIR" sudo chmod 700 "$XDG_RUNTIME_DIR" sudo...
But we are one step further now. The address is now correctly used by Chromium. Instead of "Could not parse server address", it does not try to connect to DBus...
Ah, `dbus-launch` is part of the `dbus-x11` package. However, the output of Chromium indicates it the `dbus-daemon` works. I am not sure what Chromium headless mode is supposed to do...
Interesting, so Chromium really requires upower (in headless mode) 🤔. I wonder whether this is true for kiosk mode as well. Most desktops come with upower, so it might have...
Seems like it tried to use Vulkan. In case it still appears, the driver lib might help. But generally Chromium should work well without it/OpenGLES instead: ```sh apt install mesa-vulkan-drivers...
Did you install `upower`?
Hmm, all this stuff is actually not required. Just tested on a clean NanoPi NEO3: ```sh apt install chromium dbus-run-session chromium --headless --no-sandbox --dump-dom https://dietpi.com/ ``` Throws the `upower` warnings,...
Closing this for now. Feel free to reopen if the issue persists.