-
-
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
Keyboard stops working after running pkexec swhkd
#227
Comments
Can we get some logs? |
I presume the kernel grab failed on your machine and the syscall logs would help, try strace and the swhkd logs too |
I am facing the same issue .
|
The logs seem fine, this slightly worries me ( did upstream linux break userspace? ) I have not updated any deps since last release I believe. If it's not too much of a hassle, could you guys try the latest LTS kernel once? |
ok i found the culprit . It looks like keyd daemon is somehow interfering with swhkd. I disabled the daemon via systemd and now everything is working fine. is keyd not compatible with swhkd ? |
This is interesting, we have had systemd users who also use swhkd but this situation never arrived. Does this fix work for you? @saurabhsharan I wonder if this is a regression of systemd or the kernel itself. Any runit users around who can test this hypothesis? |
Version Information:
Linux ss-archlinux 6.6.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 29 Nov 2023 00:37:40 +0000 x86_64 GNU/Linux
swhkd 1.3.0-dev
Describe the bug:
I am following the instructions to install and run swhkd. After I run
pkexec swhkd
, my keyboard becomes unresponsive and I have to reboot my machine to restore the keyboard.Expected behavior:
Keyboard should continue working after running
pkexec swhkd
.Actual behavior:
Keyboard stops working after running
pkexec swhkd
.To Reproduce:
Following instructions from README, run
swhks &
followed bypkexec swhkd
.Additional information:
Anything else you'd like us to know ?
In case it's useful information: I installed swhkd using
yay -S swhkd-git
.The text was updated successfully, but these errors were encountered: