Read-only mirror of https://gitlab.gnome.org/GNOME/mutter
d696fd3021
The seat capability updating is synchronous, but input events are asynchronous (first queued then emitted). This means we may end up in a situation where we from libinput first may receive a key event, immediately followed by a device-removed event. Clutter will first queue the key event, then remove the device, immediately triggering the seat capability removal. Later, when the clutter stage processes the queued events, the previously queued key event will be processed, eventually making it into MetaWaylandSeat. Before this patch, MetaWaylandSeat would still forward the key event to MetaWaylandKeyboard, even though it had 'released' it. Doing this would cause referencing potentially freed memory, such as the xkb state that was unreferenced when the seat removed the capability. In order to avoid processing these lingering events, for now, just drop them on the floor if the capability has been removed. Eventually, the event queuing etc needs to be redesigned to work better when used in a Wayland compositor, but for now at least don't access freed memory. https://bugzilla.gnome.org/show_bug.cgi?id=770727 |
||
|---|---|---|
| clutter | ||
| cogl | ||
| data | ||
| doc | ||
| po | ||
| src | ||
| tools | ||
| .gitignore | ||
| autogen.sh | ||
| configure.ac | ||
| COPYING | ||
| Makefile.am | ||
| mutter.doap | ||
| NEWS | ||