keymapper icon indicating copy to clipboard operation
keymapper copied to clipboard

Published 20 hours ago • verified publisher icon houmain

Keymapper stops working after some time, but only for class specific mappings

Open mark2185 opened this issue 3 years ago • 11 comments

I've had this issue for a while and now I've narrowed it down to only class specific abstract mappings.

E.g. I have things like these

# default mappings for abstract commands
  next_tab >> Ctrl{E}
  prev_tab >> Ctrl{Q}
  delete_word >> Ctrl{Backspace}

And then, in specific class names, I remap them

[class=/brave-browser|Navigator|chromium|google-chrome|betterbird|firefox/]
  next_tab >> Ctrl{Tab}
  prev_tab >> Ctrl{Shift{Tab}}

  Ext{1} >> Ctrl{1}
  Ext{2} >> Ctrl{2}
  Ext{3} >> Ctrl{3}

[class="guake"]
  next_tab >> Ctrl{PageDown}
  prev_tab >> Ctrl{PageUp}
  delete_word >> Ctrl{D}

But at some point in time (I'm not sure if it's timed with waking up from sleep, but if it is, it's not consistent) only the abstract command mappings stop working, i.e. I cannot switch tabs in firefox with capslock-e, but can jump to the first tab with capslock-1.

The capslock is also an alias.

# aliases
  Ext   = CapsLock
  Ctrl  = Control

The problem is fixed either by restarting both keymapper and keymapperd, or putting the system to sleep and waking it up again.

What else can I provide? Sadly I cannot reproduce it consistently so I'm hoping you might have a better insight into what's wrong.

mark2185 avatar Sep 26 '22 06:09 mark2185

Thanks for the report. I have no clue yet. Does it happen on Windows or Linux (X11, Wayland / Gnome or another WM)?

houmain avatar Sep 28 '22 19:09 houmain

Ah, sorry, forgot to add.

Linux, X11, i3-wm, built from latest master.

mark2185 avatar Sep 28 '22 19:09 mark2185

Additional information: it might coincide with 100% CPU usage.

mark2185 avatar Oct 13 '22 13:10 mark2185

I will check that too, it stopped to work after hours on my Fedora Silverblue

RichardFevrier avatar Oct 26 '22 10:10 RichardFevrier

journalctl does not seem very verbose about that... 😐️

RichardFevrier avatar Oct 26 '22 10:10 RichardFevrier

Welp, it happened to me an hour ago, and I didn't feel like restarting the daemon.

An hour later it miraculously started working again. :shrug:

mark2185 avatar Oct 26 '22 11:10 mark2185

@RichardFevrier are you using Wayland/Gnome?

houmain avatar Oct 26 '22 12:10 houmain

Correct!

RichardFevrier avatar Oct 26 '22 12:10 RichardFevrier

And also only mappings for a specific window class stopped working?

houmain avatar Oct 26 '22 12:10 houmain

No I think the client crashed, but I have a specific window class in my config

RichardFevrier avatar Oct 26 '22 12:10 RichardFevrier

Maybe not related to this issue tho

RichardFevrier avatar Oct 26 '22 12:10 RichardFevrier

To add (may be relevant, I don't know) - at random times, the keymapper -u command pins one CPU core at 100%.

It's still working as one would expect, but I have no idea what causes it to hog so much CPU time, I've only now added the --verbose flag so I'll report back if it happens again.

mark2185 avatar Nov 07 '22 07:11 mark2185

Thanks! I have also seen this once. I suspected two running keymapper processes to cause the problems, but I could not reproduce it.

houmain avatar Nov 07 '22 19:11 houmain

Happened again, the log looked "normal", just messages about switching focused windows, but there was a reasonable number of them.

Also there was only one keymapper process, confirmed by running pgrep -x keymapper.

mark2185 avatar Nov 10 '22 10:11 mark2185

Hi, I fixed two things in the Linux version which might have caused these problems. So please give the 2.4.0 release a try.

houmain avatar Nov 26 '22 12:11 houmain

~I've been running it since then and now it's the second time it stopped working, both occurrences coincided with high CPU usage after which keymapper --update --verbose hogs up one core at 100%.~

~The log contains nothing except Detected focused window changed blocks, and they aren't false, I did switch between those windows.~

~I'll try to reproduce it in a virtual machine with 1 CPU and will get back to you.~

~EDIT: I tried restarting only keymapper, but ultimately I had to restart keymapperd for it to start working again.~

I had two clones of keymapper and I was running the wrong one these past 3 weeks, sorry for the noise. Feel free to delete this comment after reading, I'm leaving it just for clarification. I'll get back to you if this issue appears again.

mark2185 avatar Dec 13 '22 08:12 mark2185

Unfortunately, it still happens.

keymapper pins one CPU core at 100%, certain mappings stop working, and I have to kill it and keymapperd and restart it all to get it hopefully working.

Sometimes I don't feel like doing that so I just put the laptop to sleep and wake it up again, and that may or may not fix it.

mark2185 avatar Jan 05 '23 13:01 mark2185

It looks like just restarting keymapperd is enough.

I usually started fixing it by killing keymapper since it pinned one core, but today I went with stopping the daemon first, and the CPU usage dropped to 0% after that, and after starting it again, everything seems to work.

At least it's an easy fix until we get to the bottom of this.

mark2185 avatar Jan 17 '23 14:01 mark2185

Hi @mark2185 may I ask if you are still having issues with a current version? Thanks!

houmain avatar Dec 07 '23 17:12 houmain

Now that you've mentioned it, I'm on 3.1.0 currently and don't remember hitting the same issue in these past few months (I have reinstalled OS tho).

I suggest that we close this issue, I'll update to 3.2.0 and if it starts happening again I'll reopen it :)

mark2185 avatar Dec 07 '23 17:12 mark2185

Great thanks!

houmain avatar Dec 07 '23 17:12 houmain

Unfortunately it resurfaced, a few times in the last couple of days, luckily restarting keymapperd fixes the issue.

mark2185 avatar Jan 02 '24 19:01 mark2185

I'm also experiencing this or something related. I've noticed it pretty much every morning after unlocking my computer, but also occasionally while I'm working. It doesn't reproduce simply by locking/unlocking though. I haven't yet checked if either of the processes is eating a lot of CPU, I'll check if this is the case when it happens the next time.

Some possibly relevant notes:

  • Ubuntu 20.04, i3wm
  • Keychron K15 Pro keyboard (QMK firmware)
  • keymapper is built from source with ENABLE_WAYLAND set to FALSE (tag 3.4.0)
  • keymapper has been running with the --update flag
  • I've defined various device specific mappings: keymapper.conf
  • opening and saving the config file activates the mappings again, reconnecting the keyboard does not

ristomatti avatar Jan 09 '24 17:01 ristomatti

Hi, I just fixed a problem, when two keymapper instances were running. The context updates of the second instance were not processed by keymapperd and so the send buffer could fill up until it began to busy loop... Now it knows that it is not connected.

I could not reproduce it with one process yet. Maybe keymapperd still thinks that the lock-key is still pressed and therefore does not process any context updates. I need to do some more testing.

@ristomatti, wow your configuration is really impressive!

houmain avatar Jan 09 '24 21:01 houmain

I'm pretty confident I only had a single instance. After my comment, I ran keymapper -u -v foreground to see if it would give some hints. It didn't took long for the bug to reproduce. I just had to go to get some groceries.

There was nothing on the verbose logs though, I didn't yet try with keymapperd on verbose though. System journal indicated my keyboard had disconnected and reconnected but I then remembered I disconnected it myself to charge another device. I've now built the latest version, I'll report back on the results.

Also, thanks for the kind words! I've been planning to post the config or some snippets of it on the discussion section at a later time. Keymapper has been very inspiring to say the least! It's also great for avoiding real work too... :sweat_smile:

ristomatti avatar Jan 09 '24 23:01 ristomatti

Actually, I just found at least one way to reproduce the same behavior. Both my Keychron keyboards show up with different names depending on how they're connected:

# USB-cable
$ xinput list | grep K15
⎜   ↳ Keychron Keychron K15 Pro Consumer Control	id=32	[slave  pointer  (2)]
⎜   ↳ Keychron Keychron K15 Pro Mouse         	id=37	[slave  pointer  (2)]
    ↳ Keychron Keychron K15 Pro               	id=20	[slave  keyboard (3)]
    ↳ Keychron Keychron K15 Pro System Control	id=23	[slave  keyboard (3)]
    ↳ Keychron Keychron K15 Pro Keyboard      	id=24	[slave  keyboard (3)]
    ↳ Keychron Keychron K15 Pro Consumer Control	id=36	[slave  keyboard (3)]

# Bluetooth
$ xinput list | grep K15
⎜   ↳ Keychron K15 Pro Keyboard               	id=9	[slave  pointer  (2)]
⎜   ↳ Keychron K15 Pro Mouse                  	id=17	[slave  pointer  (2)]
    ↳ Keychron K15 Pro Keyboard               	id=10	[slave  keyboard (3)]

Due to this behavior, I use a regex to match it:

[device=/Keychron K15 Pro Keyboard/]
  # ...

If I change from USB to Bluetooth or vice versa, the mappings stop working. So technically it's not the same device in this case, but should this work regardless? Typically I've had it on cable all the time, so there's something else going on though.

ristomatti avatar Jan 09 '24 23:01 ristomatti

So technically it's not the same device in this case, but should this work regardless?

Yes, multiple devices with identical names should not cause problems. Maybe you can start keymapperd with -v and check if the devices are un/grabbed as expected when plugging in/out.

houmain avatar Jan 11 '24 18:01 houmain

Will definitely do that, but it might take a while until I come back to this. Experimenting with keymapper is "somewhat" addicting. I'll need to focus a bit on actual work for a change. :grin:

Have you noticed #97 btw? I think I ran to another possibly related issue today with virtual modifiers and abstract commands. I managed to hack together an emulation of QMK's "Auto Shift" feature, then made it toggleable together with the config that allows me to write umlauts in a convenient manner. I then realized it'd be useful to somehow see when either is active. In the latest revisions of my config you'll see the initial implementation of the indicators. The indicators are shown on my i3wm status bar:

image

~~In the latest~~ With this revision, I attempted to reduce the config required for the indicators but ran into odd issue and had to just work around with lots of trial and error. I'm wondering if I've misunderstood how the config is processed or if I ran across some bugs. To explain them, I'd need too recreate them as I've already deleted the parts. That will be some later time.

But briefly, I had added two sections at the end of the file. Something like this:

[modifier="!AutoShift"]
  toggle_autoshift >> $(show_indicator) ^ AutoShift

[modifier="AutoShift"]
  toggle_autoshift >> $(hide_indicator) ^ AutoShift

This toggled the feature correctly, but regardless of the state of AutoShift, keymapper would always call the script on the lower blow. So the indicator was either always on or off.

Mainly I'd appreciate to know if I'm attempting to pull of things that aren't implemented and just happen to work by accident...

ristomatti avatar Jan 11 '24 20:01 ristomatti

I ended up trying at least the previously mentioned repro by switching between USB and Bluetooth.

Disconnect USB while mappings are working

Jan 11 23:31:21 x1e keymapperd[1113366]: Updating device list
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:31:21 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ungrabbed device event22
Jan 11 23:31:22 x1e keymapperd[1113366]: Updating device list
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:31:22 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:31:23 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:31:23 x1e keymapperd[1113366]: Ungrabbed device event258
Jan 11 23:31:23 x1e keymapperd[1113366]: Ungrabbed device event30
Jan 11 23:31:23 x1e keymapperd[1113366]: Ungrabbed device event25
Jan 11 23:31:23 x1e keymapperd[1113366]: Ungrabbed device event24

Reconnect USB -> mappings still work

Jan 11 23:32:25 x1e keymapperd[1113366]: Updating device list
Jan 11 23:32:25 x1e keymapperd[1113366]: Grabbed device event22 'Keychron Keychron K15 Pro'
Jan 11 23:32:25 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:32:26 x1e keymapperd[1113366]: Updating device list
Jan 11 23:32:26 x1e keymapperd[1113366]: Grabbed device event258 'Keychron Keychron K15 Pro Keyboard'
Jan 11 23:32:26 x1e keymapperd[1113366]: Grabbed device event30 'Keychron Keychron K15 Pro Consumer Control'
Jan 11 23:32:26 x1e keymapperd[1113366]: Grabbed device event25 'Keychron Keychron K15 Pro System Control'
Jan 11 23:32:26 x1e keymapperd[1113366]: Grabbed device event24 'Keychron Keychron K15 Pro Mouse'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:32:26 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:32:27 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:32:27 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:32:27 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:32:27 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:32:27 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'

Disconnect USB, then reconnect via Bluetooth -> mappings stop working

Jan 11 23:34:52 x1e keymapperd[1113366]: Updating device list
Jan 11 23:34:52 x1e keymapperd[1113366]: Grabbed device event22 'Keychron K15 Pro Keyboard'
Jan 11 23:34:52 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:34:53 x1e keymapperd[1113366]: Updating device list
Jan 11 23:34:53 x1e keymapperd[1113366]: Grabbed device event24 'Keychron K15 Pro Mouse'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:34:53 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:34:54 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'

touch the config file, nothing gets logged but the mappings start working again.

Disconnect Bluetooth by powering the device off while mappings still work

Jan 11 23:42:25 x1e keymapperd[1113366]: Received contexts (10)
Jan 11 23:42:25 x1e keymapperd[1113366]: Received contexts (11)
Jan 11 23:42:28 x1e keymapperd[1113366]: Updating device list
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ungrabbed device event22
Jan 11 23:42:29 x1e keymapperd[1113366]: Updating device list
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ungrabbed device event24

Reconnect via USB -> mappings again working

Jan 11 23:42:25 x1e keymapperd[1113366]: Received contexts (10)
Jan 11 23:42:25 x1e keymapperd[1113366]: Received contexts (11)
Jan 11 23:42:28 x1e keymapperd[1113366]: Updating device list
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:42:28 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ungrabbed device event22
Jan 11 23:42:29 x1e keymapperd[1113366]: Updating device list
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:42:29 x1e keymapperd[1113366]: Ungrabbed device event24

I then followed with disconnect and reconnect USB -> mappings still worked, logs skipped.

Disconnect USB and connect via Bluetooth -> mappings still work

Jan 11 23:47:13 x1e keymapperd[1113366]: Updating device list
Jan 11 23:47:13 x1e keymapperd[1113366]: Grabbed device event22 'Keychron K15 Pro Keyboard'
Jan 11 23:47:13 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'
Jan 11 23:47:14 x1e keymapperd[1113366]: Updating device list
Jan 11 23:47:14 x1e keymapperd[1113366]: Grabbed device event24 'Keychron K15 Pro Mouse'
Jan 11 23:47:14 x1e keymapperd[1113366]: Ignoring device event6 'Keymapper'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event19 'sof-hda-dsp Headphone'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event18 'sof-hda-dsp Mic'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event15 'HDA NVidia HDMI/DP,pcm=11'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event14 'HDA NVidia HDMI/DP,pcm=10'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event13 'HDA NVidia HDMI/DP,pcm=9'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event12 'HDA NVidia HDMI/DP,pcm=8'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event11 'HDA NVidia HDMI/DP,pcm=7'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event10 'HDA NVidia HDMI/DP,pcm=3'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event5 'SynPS/2 Synaptics TouchPad'
Jan 11 23:47:15 x1e keymapperd[1113366]: Ignoring device event1 'Lid Switch'

ristomatti avatar Jan 11 '24 21:01 ristomatti

I diffed the log of the earlier failed reconnect via Bluetooth after USB and this later properly working one. I can't spot anything different.. 🤔

image

ristomatti avatar Jan 11 '24 21:01 ristomatti