<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: keyboard debouncing" href="https://bugs.freedesktop.org/show_bug.cgi?id=105222#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: keyboard debouncing" href="https://bugs.freedesktop.org/show_bug.cgi?id=105222">bug 105222</a> from <a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> Olivier Fourdan</a> <pre>I think what you see here is not actually bouncing but key repeat triggering. On Wayland, key repeat is handled by the clients based on press/release events received from the compositor (as opposed to Xorg where key repeat is handled by the display server, ie the X server). If the compositor gets “busy” doing something else, it may not forward the key release fast enough and the client start repeating the key... There are some mechanisms in place in gtk+ and Xwayland to mitigate the issue, by issuing a “ping” to the Wayland compositor to makre sure it's still well alive and processing events before repeating a key, but it's not perfect and spurious key repeat can still occur under some circumstances. As a workaround, you could try increasing the key repeat delay in your compositor of choice to see if that helps with the key repeating itself. tl;dr: Nothing libinput can do to help there, it;s purely betwee nWayland client and the Wayland compositor.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>