-
-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Description
Version Information:
- Distribution Information ( run
uname -a
) 6.7.8 arch 1-1 - swhkd version (
swhkd -V
) 1.30-dev
Describe 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,
● hotkeys.service - swhkd hotkey daemon
Loaded: loaded (/etc/xdg/systemd/user/hotkeys.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-03-05 22:47:38 CET; 12s ago
Main PID: 599 (bash)
Tasks: 20 (limit: 38173)
Memory: 6.8M (peak: 20.5M)
CPU: 182ms
CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/hotkeys.service
├─599 bash /home/swer/.config/swhkd/hotkeys.sh
├─609 /usr/bin/swhkd
└─932 swhks
Mar 05 22:47:38 berserk systemd[589]: Started swhkd hotkey daemon.
Mar 05 22:47:38 berserk hotkeys.sh[608]: [2024-03-05T21:47:38Z WARN swhks::environ] XDG_DATA_HOME Variable is not set, falling back on hardcoded path.
Mar 05 22:47:38 berserk pkexec[609]: pam_unix(polkit-1:session): session opened for user root(uid=0) by swer(uid=1000)
Metadata
Metadata
Assignees
Labels
No labels