Open Canious opened 4 months ago
Hey @Canious! I have put up a proposal for this an enhancement that would fix this issue! Check it out here #251 and feel free to let me know what you think about it. Work is being done on this :)
I have seen this but how can we achieve that, I am totally a rookie. However, I saw this #144, is that what you mean @newtoallofthis123
Not per se @Canious....I mean that if swhkd detects that swhks is not running, it tries it's best to start the process as a daemon. I am still figuring out how to exactly start the daemon in itself without adding too much to the dependency graph.
How does swhkd detect if swhks is working, I am totally new to this repository, got no idea what to do about it
As far I understand, swhks
saves a file called swhks.pid
in the XDR_RUNTIME_DIR
that can be read to get the pid of the server if it is running. If it isn't we just spawn it... The spawn mechanics is something that I am trying to figure out currently
Version Information:
uname -a
) 6.7.8 arch 1-1swhkd -V
) 1.30-devDescribe the bug: I have found that swhks stops after logging in, although I have checked that swhkd is still running. I followed the systemd step and checked if it works by adding an additional autostart command to my hyprland configuration, but no luck, it doesn't work. Expected behavior: Swhks should works with swhkd after login
Actual behavior:
To Reproduce:
Additional information: I think it might be the window manager startup issue that intercepted the process, but I can't tell which one it is. And my log seems to be normal,