mirror of
https://github.com/brl/mutter.git
synced 2024-11-25 01:20:42 -05:00
4bee25d8e6
If a client is naive enough to assume that it can set the selection while it has got no surfaces, mutter will simply ignore the request and leave the selection unchanged. This is good and the expected behavior, however the poor client that did this will enter in an inconsistent state where it "claimed" the selection, but nobody told it that the wl_data_source is not current. So, when the client is focused the next time, it will receive wl_data_offers as usual, but it will still think all the time that it is owning the selection. In the case of GTK, that takes client-side shortcuts, so any attempted paste will still bring back the client-side aborted selection. To fix this, cancel the selection right away if it happened while unfocused, the client will be able to undo its own failed selection, and not assume that future offers are its own. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1469 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1772> |
||
---|---|---|
.. | ||
backends | ||
compositor | ||
core | ||
meta | ||
tests | ||
ui | ||
wayland | ||
x11 | ||
libmutter.pc.in | ||
meson.build | ||
meta-private-enum-types.c.in | ||
meta-private-enum-types.h.in | ||
org.freedesktop.login1.xml | ||
org.gnome.Mutter.DisplayConfig.xml | ||
org.gnome.Mutter.IdleMonitor.xml | ||
org.gnome.Mutter.RemoteDesktop.xml | ||
org.gnome.Mutter.ScreenCast.xml |