Alexis Janon

I am unable to reproduce this issue on my side, so this will mostly be guess work. I think there are three things which could create problems: 1. uinput device...

I managed to reproduce this on my end, I will investigate.

This was introduced in commit: af0115eb0cbd927a6ba21f5865d9e8489556db22 I will check if we can make this work or if we just revert the commit for now

I will try to run this again, but on my side it seemed to not happen before this commit, and then to happen every time swhkd is launched after this...

I am working on this. The issue is that the kernel expects the rfkill value bit (`SW_RFKILL_ALL`) to be **set** to **not** block everything. (See below for the detailed explanation)...

Just to make this clear: the `evdev` crate developers cannot do much about this, as the problem lies in the kernel. I will search through the kernel mailing lists to...

In the end, I found a better way! (see #180)

This issue is for discussion and making sure we are not forgetting anything. Notably, if we go forward with the `--device` argument deprecation, I am not sure how we should...

I'm not sure if I'll be merging this one as-is. This has not completely solved #166 and has brought other issues.

We already have a `TARGET_DIR` path in our `Makefile`, we should be able to do this automatically. Tentative implementation (in `install` target): ```diff --- a/Makefile +++ b/Makefile @@ -25,6 +25,7...