Volume keys repeat with K400+ keyboard when used through a KVM switch

[Andy Owen]

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.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: 2023-01-29 19:21:52,446 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroRelease: Ubuntu 22.04
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Picasso [1458:d000]
InstallationDate: Installed on 2021-08-20 (534 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
Package: libinput (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Tags: wayland-session jammy ubuntu
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: Upgraded to jammy on 2023-01-29 (7 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/24/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F60
dmi.board.asset.tag: Default string
dmi.board.name: B450 I AORUS PRO WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF60:bd02/24/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450 I AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Andy Owen (the-new-andy)]

The keyboard appears as /dev/input/event[3, 12, 13, 14, 15] but the recording I provided was just for event14 (which I think is the correct one). I do have a recording with all the event sources, but launchpad won't let me upload it for some reason (tried a few times). Can get it if needed.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2006043/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

Moving to libinput which you suspect is the affected package as few developers will see this bug report if it is left here. If another package is found to be at fault then it can always be moved on again.

In the meantime please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 2006043

When reporting bugs in the future please use apport in a terminal by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

apport information

[Andy Owen (the-new-andy)]

So sorry, I just realised I left out a key bit of information. There is also a KVM in the mix which is required to reproduce:

I am using one of these:

https://www.4cabling.com.au/4k-kvm-console-extender-with-poc-over-cat6-6a-70m-with-hdmi-loop-through.html

With the usb wireless dongle plugged into the KVM. When the dongle is plugged directly into the computer (which it was when I ran apport-collect), then the key function correctly.