Antoine DAMHET
Antoine DAMHET
That's expected. The fedora package is using logind for unprivileged operations the build/install process looks like: ``` $ make ENABLE_SYSTEMD=1 $ [sudo] make install INSTALL_UDEV_RULES=0 ENABLE_SYSTEMD=1 PREFIX=/usr ``` And if...
`sd_notify` internal support probably won't happen: https://github.com/swaywm/sway/pull/3486
https://lwn.net/Articles/833247/
https://systemd.io/DESKTOP_ENVIRONMENTS/
`sway.service` should only bring up the `*-session-pre.target` and the `*-session.target` should be started via the config file. I need to figure-out the "cleanest" way to do it **and** how to...
I thought `sway-user-service` would always be launched by a login manager (maybe it should be somewhere outside the $PATH or I could take extra steps to support the use case)....
I may have some bugs letting the (systemd's) environment polluted. If you reproduce the failure of `systemctl --user start sway`, it would be helpful if you dumped me (right after):...
Sorry, I did'nt took the time to look into it lately. But yeah it's environment related. I'm trying to figure out witch variable is needed and why. I now think...
@robbat2 did you have time to look ? as a side-note the code is running on multiple thousand of machines since late February without issue yet
The idea is to setup wayland specific environment values like: ``` MOZ_ENABLE_WAYLAND SDL_VIDEODRIVER ``` etc.