Created attachment 172170 [details] video of pressing the mute key several times SUMMARY I have a laptop with a speaker mute key that sends events via both the hid keyboard and the Dell WMI hotkeys devices. Because of this, I am unable to use the mute key to mute my speakers. This issue only manifests with Plasma on Wayland, not X11. Mutter filters these keys like this, not sure if it's relevant: ``` { MUTE_KEY, "volume-mute", TRUE, SHELL_ACTION_MODE_ALL, META_KEY_BINDING_IGNORE_AUTOREPEAT }, ``` STEPS TO REPRODUCE 1. Press speaker mute key OBSERVED RESULT Speakers quickly mute and unmute EXPECTED RESULT Speakers toggle their muted state SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux kernel 6.10.2-arch1.1 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION enabled arch kde-unstable repository, bug persists Laptop model: Dell G16 7620 -event20 DEVICE_ADDED HID 0d62:3740 Keyboard seat0 default group5 cap:kp scroll-nat -event7 DEVICE_ADDED Dell WMI hotkeys seat0 default group10 cap:k -event20 KEYBOARD_KEY +0.000s KEY_MUTE (113) pressed -event7 KEYBOARD_KEY +0.019s KEY_MUTE (113) pressed event7 KEYBOARD_KEY +0.019s KEY_MUTE (113) released -event20 KEYBOARD_KEY +0.111s KEY_MUTE (113) released See also latest discussion on this Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003161
IMO shouldn't it be the responsibility of the driver to make sure that we don't get two events from two different devices?
(In reply to fanzhuyifan from comment #1) > IMO shouldn't it be the responsibility of the driver to make sure that we > don't get two events from two different devices? In the Launchpad bug I mentioned the person who wrote that part of the driver recommended it be put in userspace. I think part of the issue is that devices send the event from the keyboard, from the WMI device, or both.
Ok on git master (wayland) I cannot reproduce by simulating the situation by simultaneously using two keyboards with the mute key. So I plugged in two keyboards, and press both mute keys simultaneously multiple times. I ran `sudo libinput debug-events --show-keycodes` and got the following events: ``` -event7 KEYBOARD_KEY +4.568s KEY_MUTE (113) pressed -event5 KEYBOARD_KEY +4.570s KEY_MUTE (113) pressed -event7 KEYBOARD_KEY +4.646s KEY_MUTE (113) released -event5 KEYBOARD_KEY +4.699s KEY_MUTE (113) released event5 KEYBOARD_KEY +5.875s KEY_MUTE (113) pressed -event7 KEYBOARD_KEY +5.886s KEY_MUTE (113) pressed event7 KEYBOARD_KEY +5.955s KEY_MUTE (113) released -event5 KEYBOARD_KEY +6.003s KEY_MUTE (113) released event5 KEYBOARD_KEY +7.404s KEY_MUTE (113) pressed -event7 KEYBOARD_KEY +7.427s KEY_MUTE (113) pressed event7 KEYBOARD_KEY +7.496s KEY_MUTE (113) released -event5 KEYBOARD_KEY +7.515s KEY_MUTE (113) released ``` Note that this should be equivalent to the sequence of events generated in the original report. However, each press still correctly mutes/unmutes the audio -- it is as if only a single press is emitted. In particular, if I open kwin debug console (search for that in krunner) and go to events, I only see a single pair of press and release events there. There are two possibilities: 1. Simulating the issue with two different keyboards this way is actually different from the issue. 2. For some reason the issue is fixed in git master.
Given that I *can* reproduce on plasma 6.1 wayland, let's call this fixed in plasma 6.2. There has been some changes to input handling, but I am not sure which commit exactly solved the issue. Feel free to reopen if the issue persists for you on plasma 6.2, or current git master.
I'm already on kde-unstable, do you know if there is an easy way to use 6.2 on Arch without building it all myself? Upgrading one package would be great but I'm okay with a few, as long as it's not the whole desktop environment. Looking into AUR helpers in the meantime, since it would be unreasonable to manage all of that myself.
(In reply to James R Larrowe from comment #5) > I'm already on kde-unstable, do you know if there is an easy way to use 6.2 > on Arch without building it all myself? Upgrading one package would be great > but I'm okay with a few, as long as it's not the whole desktop environment. > > Looking into AUR helpers in the meantime, since it would be unreasonable to > manage all of that myself. Plasma 6.2 hasn't been released yet, so it is not in kde-unstable. Garuda used to maintain a repo containing git builds of everything. I am not sure if it is still maintained (https://forum.garudalinux.org/t/kde-6-repository-testing/31442/26) If you just want to test things out you should try a neon unstable live usb disk. That is the least disruptive way to see if things are fixed for you in the upcoming 6.2 release. I run the full git session via kdesrc-build (https://community.kde.org/Get_Involved/development). But that's a ton of stuff to compile. If you just want to upgrade a few packages, my hunch is that kwin might be the package containing the fix. So you might want to try just compiling the git version of that.