<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Xwayland crashes when seat adds a capability and sends some input event" href="https://bugs.freedesktop.org/show_bug.cgi?id=81819#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Xwayland crashes when seat adds a capability and sends some input event" href="https://bugs.freedesktop.org/show_bug.cgi?id=81819">bug 81819</a> from <a class="email" href="mailto:mforney@mforney.org" title="Michael Forney <mforney@mforney.org>"> Michael Forney</a> <pre>Partially. The commit you referenced fixes the case where a seat capability disappears and then reappears (such as when disconnecting then reconnecting a mouse, or switching VTs). However, if Xwayland is started without some capability (for example, no pointing devices connected), then a mouse is plugged in, the problem remains. This is can be reproduced by starting weston with no pointing devices, switching to another VT, launching weston-terminal (by setting WAYLAND_DISPLAY), switching back to the weston VT, launching an X client in the opened terminal (by setting DISPLAY), then plugging in a mouse and moving the cursor over the X client. The issue is that the devices created after Xwayland startup are never activated.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>