[BUG] Fails to run on Slackware unless *another* wayland session is already running.

[Charadon]

Describe the bug
If no other wayland session is running on another tty on the same user, veshell will hang on the loading screen forever. This is reproducible on the latest commit.

To Reproduce
Steps to reproduce the behavior:

1. Clone repo
2. Run make build && make package
3. Login to tty, and run LD_LIBRARY_PATH=/usr/local/lib/veshell dbus-run-session veshell --session or LD_LIBRARY_PATH=/usr/local/lib/veshell dbus-run-session veshell
4. Infinite loading screen

Expected behavior
The compositor launches and shows the shell.

Screenshots
N/A

Additional context
Only thing I can give is a log file with RUST_LOG=debug set:

veshell.log

At a glance, it doesn't look like anything is going wrong. But there is some oddites: The XWayland session that veshell launches does not have the WAYLAND_DISPLAY env var set, and I noticed that the rust code tries to run systemctl to populate some env variables, which is probably not good practice. (I've not seen any other compositor do something like that)

[PapyElGringo]

You don't have systemd?

the /bin/sh: line 1: systemctl: command not found
The rust code is there to provide the Compositor Env for portals to works

[Charadon]

Yeah, slackware doesn't have systemd, the main concern with that is veshell won't be able to run on other distros such as alpine, or even BSDs. I don't know how other compositors such as sway and kde do it, but they work fine with just a normal dbus-run-session.

It's still very odd that if KDE is running on TTY1, veshell will launch just fine, but if it's not running, it'll hang.