| 2022-01-07 03:31:26 +0100 | neurocyte0917 | (~neurocyte@IP-046243081042.dynamic.medianet-world.de) |
| 2022-01-07 03:31:26 +0100 | neurocyte0917 | (~neurocyte@IP-046243081042.dynamic.medianet-world.de) (Changing host) |
| 2022-01-07 03:31:26 +0100 | neurocyte0917 | (~neurocyte@user/neurocyte) |
| 2022-01-07 03:33:29 +0100 | neurocyte091 | (~neurocyte@user/neurocyte) (Ping timeout: 256 seconds) |
| 2022-01-07 03:33:29 +0100 | neurocyte0917 | neurocyte091 |
| 2022-01-07 10:48:47 +0100 | neurocyte091 | (~neurocyte@user/neurocyte) (Quit: The Lounge - https://thelounge.chat) |
| 2022-01-07 10:49:59 +0100 | neurocyte0917 | (~neurocyte@IP-046243081042.dynamic.medianet-world.de) |
| 2022-01-07 10:49:59 +0100 | neurocyte0917 | (~neurocyte@IP-046243081042.dynamic.medianet-world.de) (Changing host) |
| 2022-01-07 10:49:59 +0100 | neurocyte0917 | (~neurocyte@user/neurocyte) |
| 2022-01-07 16:46:36 +0100 | kraM | (~kraM@user/kram) |
| 2022-01-07 16:50:16 +0100 | <kraM> | Hey guys. I have a working setup on node a which I want to use on node b as well. https://paste.xinu.at/HfONk/ xcape like: Have CAPS used as ESC on short keypress, as META when holding it down. |
| 2022-01-07 16:50:17 +0100 | GavinFreeborn[m] | (~gavinokma@2001:470:69fc:105::cb9) |
| 2022-01-07 16:50:17 +0100 | contessa | (~contessa@2001:470:69fc:105::a9f) |
| 2022-01-07 16:50:17 +0100 | Tisoxin | (~ikosit@user/ikosit) |
| 2022-01-07 16:50:17 +0100 | meain | (~meain@2001:470:69fc:105::2db) |
| 2022-01-07 16:50:57 +0100 | <kraM> | On node b activating this configuration results in the Enter key doing nothing anymore. I have no idea what I'm doing and what this configuration exactly tells me. |
| 2022-01-07 16:51:15 +0100 | <kraM> | (Did this once with some guy who understands kmonad.) |
| 2022-01-07 16:51:39 +0100 | <kraM> | Anything reasonable in what I said and any idea where I might want to learn more? |
| 2022-01-07 16:53:26 +0100 | <kraM> | Ah. Hm. I fear the input device I'm targeting on node b isn't exactly the keyboard only. It seems to disable the touchpad completely as wall. |
| 2022-01-07 17:07:25 +0100 | <kraM> | Okay. I guess I understand what happens, but I have no idea how to address this. From kernel point of view I only have /dev/input/by-path/platform-i8042-serio-0-event-kbd only. |
| 2022-01-07 17:11:10 +0100 | <kraM> | Hm. Nope. cat $device doesn't do anything when moving the mouse via touchpad. |
| 2022-01-07 17:16:12 +0100 | <kraM> | So, device-file seems to be correct, kmonad configuration looks legit (as far as I understand), but touchpad and enter key on internal keyboard stop working. Any hint greatly appreciated! |
| 2022-01-07 17:29:36 +0100 | <neurocyte0917> | kraM, maybe evtest can tell you more about what is going on? |
| 2022-01-07 17:33:28 +0100 | <kraM> | sudo evtest -> choose input 4 -> press Enter -> all fine. Start kmonad, press Enter -> new blank line in terminal, EV_MSC or EV_KEY output. |
| 2022-01-07 17:33:55 +0100 | <kraM> | Ah. Sure. Um. kmonad creates a virtual keyboard, right? |
| 2022-01-07 17:34:42 +0100 | <kraM> | Right. Now I'm completely confused. |
| 2022-01-07 17:37:29 +0100 | <kraM> | Reason for my confusion: sudo systemctl start kmonad -> broken. Running as unprivileged user -> everything works as expected. |
| 2022-01-07 17:37:57 +0100 | <kraM> | A wayland thing, maybe? |
| 2022-01-07 17:38:47 +0100 | <kraM> | Like, root/sudo doesn't know about the wayland session, does something, and sway doesn't recognize any new input devices (or something like that)? |
| 2022-01-07 17:39:49 +0100 | <kraM> | (Node a is a desktop with xorg and everything feels simpler. Node b is a notebook with wayland/sway.) |
| 2022-01-07 17:44:47 +0100 | <neurocyte0917> | I use kmonad with wayland all the time. It should work fine. |
| 2022-01-07 17:46:04 +0100 | <neurocyte0917> | and evtest with the kmonad virtual device doesn't produce any events at all? |
| 2022-01-07 17:50:19 +0100 | <kraM> | kmonad device gives me, e.g.: type 1 (EV_KEY), code 28 (KEY_ENTER), value 1 |
| 2022-01-07 17:51:28 +0100 | <kraM> | (Need to do that via ssh right now. Currently I don't have any Enter key functionality again, whatever user I start the service with.) |
| 2022-01-07 17:51:57 +0100 | <kraM> | ESC/LMET an CAPS is working fine though. |
| 2022-01-07 17:52:10 +0100 | kraM | is confused. |
| 2022-01-07 17:52:48 +0100 | <Solid> | that sounds weird indeed |
| 2022-01-07 17:54:55 +0100 | <kraM> | So to sum up: I guess there's nothing horrible wrong with my kmonad keyboard definition, right? |
| 2022-01-07 17:55:03 +0100 | <Solid> | not that I can see |
| 2022-01-07 17:56:30 +0100 | <kraM> | That's good. Checkmark. |
| 2022-01-07 17:58:35 +0100 | <kraM> | kmonad seems to do everything correctly. It grabs on the physical keyboard, creates a virtual one, and evtest recognises keypress events on virtual keyboard correctly. |
| 2022-01-07 17:58:38 +0100 | <kraM> | Checkmark. |
| 2022-01-07 17:59:52 +0100 | <kraM> | In sway I cannot launch terminals (LMET+Enter) and in running terminals (alacritty) pressing Enter does nothing after starting kmonad. I'll test some gui application. |
| 2022-01-07 18:02:36 +0100 | <kraM> | No Enter functionality in wayland native gui application. No Enter functionality in Xorg (xlsclients) application. |
| 2022-01-07 18:04:25 +0100 | <kraM> | For idiots: Should I disable `input "*" { xkb_options "caps:escape" }` in sway? |
| 2022-01-07 18:05:04 +0100 | Solid | has no idea about Wayland as he will cling to X11 for at least another 10 years |
| 2022-01-07 18:07:36 +0100 | <kraM> | As far as I understand these xkb_options shouldn't bother kmonad. |
| 2022-01-07 18:07:51 +0100 | <Solid> | they should not |
| 2022-01-07 18:08:07 +0100 | <Solid> | kmonad reads directly from uinput, long before any environment has a chance to change the keys |
| 2022-01-07 18:08:30 +0100 | <kraM> | Thought so. |
| 2022-01-07 18:11:21 +0100 | <kraM> | Okay. Thank you guys for rubberducking. I'll give up for today. I still appreciate any further hint. |
| 2022-01-07 18:20:18 +0100 | <neurocyte0917> | kraM, now that I think about it, I remember having similar problems with kmonad and wayland to you. My "fix" was to start kmonad before wayland (via systemd on startup) and since then I've had no problems. |
| 2022-01-07 18:20:40 +0100 | <kraM> | I'll give that a try. |
| 2022-01-07 18:22:18 +0100 | <kraM> | Works. |
| 2022-01-07 18:22:59 +0100 | <kraM> | When it's not the simple things to fix an issue, it's the more simple things. |
| 2022-01-07 18:23:39 +0100 | <kraM> | such happy much wow very thanks |
| 2022-01-07 18:23:48 +0100 | Solid | adds that to his bucket list of reasons why wayland is not ready yet :> |
| 2022-01-07 18:27:36 +0100 | <kraM> | A lot of things feel quite good nowadays with wayland, assumed not to use nvidia proprietary drivers. |
| 2022-01-07 18:27:53 +0100 | <kraM> | Especially if you come from i3 and go to sway. |
| 2022-01-07 18:29:41 +0100 | <neurocyte0917> | The nvidia drivers are catching up quickly in the last few months. I have a nvidia desktop running wayland and most things work just fine. Not everything though. |
| 2022-01-07 18:30:03 +0100 | <Solid> | kraM: I do not |
| 2022-01-07 18:30:22 +0100 | <Solid> | I suspect that to feel at home on Wayland we would need to port my current wm to it |
| 2022-01-07 18:30:36 +0100 | <Solid> | (and we will, at one point) |
| 2022-01-07 18:30:59 +0100 | <kraM> | I'll stick to Xorg on my desktop with nvidia. Desktop/wm is one thing, games, ... Before I did that, I'd buy an AMD GPU. |
| 2022-01-07 18:31:00 +0100 | <Solid> | but I still object to some fundamental architectural decisions so... it'll probably never feel quite right :/ |
| 2022-01-07 18:31:18 +0100 | <kraM> | What wm are you using, Solid? |
| 2022-01-07 18:31:31 +0100 | <Solid> | kraM: xmonad (of course!) |
| 2022-01-07 18:31:56 +0100 | <neurocyte0917> | sway is a bigger problem than wayland for me. i3 just works. sway has some catching up to do. |
| 2022-01-07 18:32:31 +0100 | <neurocyte0917> | I used xmonad for many years. I switched to i3 at some point, but I don't really remember why. |
| 2022-01-07 18:32:36 +0100 | <kraM> | Hm. Ja. I'm too stupid for xmonad, herbstluftwm is missing a feature I'm used to too much (and hlwm is xlib only), so i3/sway it is for me. |
| 2022-01-07 18:33:37 +0100 | <Solid> | no one's too stupid for xmonad---the website even says "that was easy!" :P |
| 2022-01-07 18:35:05 +0100 | <kraM> | neurocyte0917: Did you say you run wayland with i3? |
| 2022-01-07 18:35:37 +0100 | <Solid> | I think they meant they switched xmonad -> i3 on X11 and then to sway for wayland |
| 2022-01-07 18:36:18 +0100 | <kraM> | xcb is X only, right? |
| 2022-01-07 18:36:24 +0100 | <Solid> | yes |
| 2022-01-07 18:38:09 +0100 | <kraM> | That would've grinded my gears, if switching to sway wasn't necessary. |
| 2022-01-07 18:44:17 +0100 | <drdo> | I run wayland and kmonad works well. But I have had very strange issues when working with evdev directly myself |
| 2022-01-07 18:44:53 +0100 | <drdo> | Even though the generated events were exactly the same I sometimes got strange results in terminals depending on how fast I emitted the events |
| 2022-01-07 18:45:02 +0100 | <drdo> | I never figured it out |