I suspect this is a big for libinput, but I find this all a bit confusing.
When I press the volume up/down keys on a Logitech K400+ keyboard, pressing either key once behaves as if I have held the key down - this state persists until another key is pressed (e.g. if I press volume up, then the volume will quickly increase to maximum, and then if I try to adjust the system volume with the mouse, when I release the mouse, the volume again returns to full - but if I press "escape", then it realises the key is not held.
I am including the libinput event logs, and debug logs for pressing "volume+", "volume-", "volume+", "volume-", "escape". When I try to replay the log with libinput replay, the behaviour I'm observing is just just as if I pressed "volume-", so I'm not quite sure what is going on here.
This keyboard was working fine with Ubuntu 21.10, it is only after upgrading to 22.04.1 that this problem has started happening. I tried both Wayland and Xorg sessions, and both had the same problem. I have libinput10 version 1.20.0-1ubuntu0.2 installed.
I suspect this is a big for libinput, but I find this all a bit confusing.
When I press the volume up/down keys on a Logitech K400+ keyboard, pressing either key once behaves as if I have held the key down - this state persists until another key is pressed (e.g. if I press volume up, then the volume will quickly increase to maximum, and then if I try to adjust the system volume with the mouse, when I release the mouse, the volume again returns to full - but if I press "escape", then it realises the key is not held.
I am including the libinput event logs, and debug logs for pressing "volume+", "volume-", "volume+", "volume-", "escape". When I try to replay the log with libinput replay, the behaviour I'm observing is just just as if I pressed "volume-", so I'm not quite sure what is going on here.
This keyboard was working fine with Ubuntu 21.10, it is only after upgrading to 22.04.1 that this problem has started happening. I tried both Wayland and Xorg sessions, and both had the same problem. I have libinput10 version 1.20.0-1ubuntu0.2 installed.