| 2023-01-14 01:03:43 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Ping timeout: 260 seconds) |
| 2023-01-14 07:37:10 +0100 | <n0r> | I don't know what keyboard you have, but on most it can't be remapped. That is because pressing it does not send a signal to the OS - or even the CPU - but is a layer-toggle handled by the keyboard hardware itself. KMonad can't change how the keyboard hardware behaves. Shift, Control, Alt etc. are modifier keys handled by the OS and therefor can be changed in the OS. Also see here: |
| 2023-01-14 07:37:10 +0100 | <n0r> | https://github.com/kmonad/kmonad/blob/master/doc/faq.md#q-why-cant-i-remap-the-fn-key-on-my-laptop |
| 2023-01-14 07:51:39 +0100 | <Solid> | they already seem to have disappeared |
| 2023-01-14 08:33:05 +0100 | <n0r> | Oh right I didn't realize this is IRC where people don't stay long 😅 |
| 2023-01-14 09:11:07 +0100 | <Solid> | wouldn't be fun otherwise :) |
| 2023-01-14 12:06:51 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 12:07:13 +0100 | <raccct> | anyone using kmonad with sway? |
| 2023-01-14 12:07:40 +0100 | <n0r> | Not currently, but I used to. |
| 2023-01-14 12:08:52 +0100 | <raccct> | n0r: do I have to disable something in sway to get kmonad to be able to grab IOCTL? kmonad can't get a hold of my keyboard since sway is using it |
| 2023-01-14 12:11:50 +0100 | <n0r> | I never had this issue, probably because I was always starting kmonad before sway launched (as a systemd service). |
| 2023-01-14 12:12:52 +0100 | <raccct> | n0r: thanks for the hint. a reboot might be necessary to get kmonad loaded first maybe. |
| 2023-01-14 12:12:55 +0100 | <n0r> | I mean: Kmonad as a service. Therefore also active in tty and even before logging in. |
| 2023-01-14 12:13:42 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Quit: Client closed) |
| 2023-01-14 12:18:12 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 12:19:37 +0100 | <raccct> | n0r: reboot didn't do the trick. kmonad is running as a service (enabled). config there. but no effect. when I try to run kmonad config.kbd manually I get: kmonad: Could not perform IOCTL grab on: /dev/input/event4 |
| 2023-01-14 12:21:21 +0100 | <raccct> | when I check with `fuser -v /dev/input/event4` I get PID: 975 F.... sway |
| 2023-01-14 12:22:43 +0100 | <raccct> | what else could I try? |
| 2023-01-14 12:23:20 +0100 | <n0r> | Is the service wantedBy multi-user.target ? |
| 2023-01-14 12:26:09 +0100 | <raccct> | wantedBy=default.target so I change that and try again. thanks! |
| 2023-01-14 12:29:00 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Quit: Client closed) |
| 2023-01-14 12:31:59 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 12:33:28 +0100 | <raccct> | n0r: no luck :( - still sway capturing the keyboard |
| 2023-01-14 12:34:43 +0100 | <raccct> | what more could I try? |
| 2023-01-14 12:36:32 +0100 | <n0r> | Well, at least sway isn't the responsible one since KMonad now definitely should be trying to first, but fails where sway succeeds later. |
| 2023-01-14 12:40:19 +0100 | <n0r> | So how about permissions? Is KMonad even allowed to mess with the input system? It should run as a user with certain permissions. Afaik that means the groups "input" and "uinput", but don't quote me on that. I just ran it as root. |
| 2023-01-14 12:49:17 +0100 | <raccct> | yup. had added input and uinput groups to my user. now also tried to run `sudo kmonad config.kbd` still gives: kmonad: Could not perform IOCTL grab on: /dev/input/event4 |
| 2023-01-14 12:51:11 +0100 | <n0r> | Can't help you any further unfortunatly. It "just worked" for me so I never investigated details of this. |
| 2023-01-14 12:51:42 +0100 | <raccct> | n0r: no worries. thanks for the hints tho! |
| 2023-01-14 13:31:25 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Quit: Client closed) |
| 2023-01-14 14:50:47 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 15:05:15 +0100 | Diablo-D3 | (foobar@exelion.net) (Ping timeout: 268 seconds) |
| 2023-01-14 15:14:21 +0100 | Diablo-D3 | (foobar@exelion.net) |
| 2023-01-14 15:24:14 +0100 | Diablo-D3 | (foobar@exelion.net) (Remote host closed the connection) |
| 2023-01-14 15:24:49 +0100 | Diablo-D3 | (foobar@exelion.net) |
| 2023-01-14 15:31:51 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Quit: Client closed) |
| 2023-01-14 15:38:24 +0100 | <Diablo-D31> | raccct: try unplugging and replugging the keyboard? |
| 2023-01-14 15:38:24 +0100 | <Diablo-D31> | oh wait |
| 2023-01-14 15:38:24 +0100 | <Diablo-D31> | it wont even with sudo? weird |
| 2023-01-14 18:20:34 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 19:44:53 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) (Ping timeout: 260 seconds) |
| 2023-01-14 20:41:00 +0100 | Guest13 | (~Guest13@64.42.177.150) |
| 2023-01-14 20:42:06 +0100 | Guest13 | (~Guest13@64.42.177.150) (Client Quit) |
| 2023-01-14 23:41:20 +0100 | raccct | (~raccct@2001:1711:fa56:7900:8022:98aa:bb6d:77ef) |
| 2023-01-14 23:42:44 +0100 | <raccct> | n0r: just wanted to let you know I have managed to get it working - thanks for the swing! :) |
| 2023-01-14 23:49:02 +0100 | <raccct> | I run linux on a mac keyboard which has some special keys that I cannot put in defsrc because kmonad complains. In Keycodes.hs there is a if_DARWIN_HOST_OS condition. So I can't use those restricted keys (like fn, lp, mctl) in linux on mac hardware? Can I somehow remap them in kmonad? |