Sebastian Keller dbd6e74d3c x11: Let selection input streams create their own window ... When there are two (or more) concurrent XConvertSelection requests with the same target, selection and window and the data is large enough for SelectionNotify events to overlap. This can result in the affected streams being considered completed without any data being transferred. While regular mutter/shell code does not make use of concurrent XConvertSelection requests with the same targets, some extensions might. Such as for example a clipboard manager that like the built-in clipboard manager tries to read the selection on owner-changed. One potential solution would be to make sure the event is for the correct property, but not all clients seem to support concurrent requests for the same targets but different properties on the same window. This commit instead changes the streams to use their own window which seems to be more widely supported. Fixes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4034 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1812>		2022-01-07 02:21:28 +01:00
..
backends	wayland: Use new KMS update test API to try acquiring scanout	2022-01-05 20:00:36 +00:00
compositor	plugins/default: Fix broken switch_workspace()	2022-01-06 16:49:25 +00:00
core
meta
tests
ui
wayland	wayland: Drop deprecated text input	2022-01-05 22:30:21 +00:00
x11	x11: Let selection input streams create their own window	2022-01-07 02:21:28 +01:00
libmutter.pc.in
meson.build	wayland: Drop deprecated text input	2022-01-05 22:30:21 +00:00
meta-private-enum-types.c.in
meta-private-enum-types.h.in