Hello all,
It is my first time using Artix and I have a week old install set up with linux-zen, runit, elogind and Sway.
Here is a description of the issue I'm facing:
On a tty, before launching Sway, issuing `loginctl suspend` works as expected.
Sway is launched ( with `exec dbus-run-session sway`, if that matters... ) and I open a terminal.
Now, if I issue `loginctl suspend` it starts the suspension process. It disables the network, locks the screen (I have this set up on .config/sway/config), but the screen is not turned off and it seems the suspension process stops there.
In this state I can unlock the screen and use the terminal but `loginctl` commands doesn't work properly. I have to reboot the system to get it working correctly again (with `sudo reboot`, `loginctl reboot` doesn't work).
Now, if instead of using `loginctl`, I issue `cat mem >| /sys/power/state` from a terminal inside Sway, the system suspends successfully, but, of course, doesn't go through the `before-sleep` steps I have in .config/sway/config and leaves the session unlocked.
Does anyone faces the same issue as me?
On the same machine I have an Arch install with basically the same setup, but, of course, using systemd, and I don't have this issue there. Could this be a bug then on elogind or Sway's integration with it?
I'll boot up my Artix install again and I'll get the `/var/log/everything.log` to put here as a new comment below
Here is the everything.log after I issue `loginctl suspend`
No other information is printed out...
I would think this is an upstream issue. Maybe something to do with libseat.
I ended up moving to seatd for seat management (in lieu of elogind) and now I can suspend with `loginctl suspend`.
Of course, there is no integration anymore between sway and loginctl and `swayidle before-sleep ...` stuff doesn't work.
I'm putting the `before-sleep` steps in a /lib/elogind/system-sleep/sway-before-sleep.sh script now.