-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd service not starting on startup altough is enabled #202
Comments
this is the output after running
I will upgrade to last version and write if it fixed itself or if something is different in the latest git version |
Ok, no changes after upgrade, i also see what happened if i restarted 2 times in a row without intevention, but same error as first message, if you guys need more info about the service, here is the service itself located at /etc/systemd/user/hotkeys.service
And here is the script itself
|
i realized im also not being able to start the system again, here are the journalctl logs
so i tried killing swhkd with sudo and also killed swhks and restart the service again, got a different behaviour
|
I realized why, idk what happened but my swhkd config file /etc/swhkd/swhkdrc was erased from existence, putting it back seems to make it work, i now shall see if with some tweaking i can make it work properly on startup |
i havent seem to find a way to make it work on startup, i dont even know what could work tbh |
Version Information:
uname -a
)Linux arch 6.2.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 20 Apr 2023 16:11:55 +0000 x86_64 GNU/Linux
swhkd -V
)swhkd 1.3.0-dev
Describe the bug:
Swhkd service does not start correctly on startup altough i have the service enabled, so every time i log in i have to manually restart it
Expected behavior:
the service starting correctly on startup
Actual behavior:
the service not starting correctly on startup
To Reproduce:
install the git version via aur and follow the systemd guide in this repo but specifying some devices
Additional information:
Anything else you'd like us to know ?
yes, here is the output of
systemctl --user status hotkeys.service
or by using journalctl, is the sameThe text was updated successfully, but these errors were encountered: