wretchedneo

> I'm wondering to myself if D-Bus is just unavailable? Are you starting the graphical session with `dbus-launch`? If not, how are you starting it? I have dbus enabled as...

> I'm confused as to the correctness of the script. You seem to be chaining `exec` calls one after the other, and using the `&` to background the exec call,...

> With that, your user services are in the background and your dbus-enabled LXQt graphical session takes over the shell process that launched it. I am still seeing the same...

> I do need to ask though, how are you starting elogind? I don't actually know, I neither have it as a service in runit, nor am I spawning it...

https://github.com/lxqt/lxqt/issues/2732 I tried it, but they told me to come here. I will try to open another issue.

> I don't recommend opening a new ticket, they'd likely file it as a duplicate (seeing as it is), just have them know that LXQt is attempting to send session...

> I'd probably ask around IRC (`#voidlinux`) if there exists any blocker for `lxqt` being set to `2.2.0`, most (if not all) other packages are set to `2.2.0`. It would...

> I advised you against activating it manually because Void Linux should configure `elogind` such that D-Bus launches it properly for you without any manual intervention on your part. Indeed...

> Relevant pull request that may resolve this specific issue: [#55900](https://github.com/void-linux/void-packages/pull/55900) I haven't tried the Wayland session yet, will give this a try today

something similar has lately started happening with lxqt-runner ``$ lxqt-runner QCssParser::parseColorValue: Specified color with alpha value but no alpha given: 'rgba 20, 20, 20' systemd: "CanHibernate" = "na" ** Dbus...