https://bugs.kde.org/show_bug.cgi?id=491097
--- Comment #3 from fanzhuyi...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
