<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Input Stops When Wayland Client Freezes" href="https://bugs.freedesktop.org/show_bug.cgi?id=99645#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Input Stops When Wayland Client Freezes" href="https://bugs.freedesktop.org/show_bug.cgi?id=99645">bug 99645</a> from <a class="email" href="mailto:antoine.saroufim@gmail.com" title="Antoine Saroufim <antoine.saroufim@gmail.com>"> Antoine Saroufim</a> <pre>It's not just Mutter. Retroarch can run on Wayland directly without an intermediary client (it acts as its own client) and it displayed the same behavior too. When it couldn't grab the input, nothing else did and the system stopped receiving input altogether. What I'm trying to say is that one system component or the other should always be ready to grab the input if the Wayland client releases it or at least always be ready to respond to certain keyboard configurations such as the panic button combination (control + alt + delete pressed repeatedly) to rescue the system. With X, it was possible to kill the X server and force it to restart by hitting a certain keyboard combination (control alt backspace if enabled). I understand that the Wayland protocol itself might not be the right component to handle such a situation but I am not entirely sure who should. The kernel? systemd? Libinput? The wayland clients themselves? I'm not entirely sure where to take this issue up and that's why I brought it here.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>