Use a typedef for MetaRemoteDesktop, so tests poking MetaBackend don't indirectly depend upon generated headers. This is arguably a code fix for a build system bug. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1470 Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1449 (or something...) (cherry picked from commit e0944b6097566dee3a09a919ba49a071e0137f26)
Qt sets window geometry without in the same commit providing actual content matching it, and relies on the compositor being able to adapt without a new window geometry on a later commit. Other compositors do this, so do the same, even though it's not guaranteed according to spec. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1557 (cherry picked from commit f5b44be9f22efd59b34dd8c3a98328306f979eea) https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1559
This happens due to Qt doing wierd things, committing incomplete and incorrect state. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1559
This is similar to commit b9e5a2d6e23, but for the X11 backend. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1466 Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1495 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1553 (cherry-picked from commit b6211bb6842fd7f88bc4f70f0d268614b85f4b3d)
These devices in x11 are "disabled", that doesn't mean we should refrain from notifying about them. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1476 Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1496 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1553 (cherry-picked from commit 34710eabc0dc2154d26296f3121728683af4afe6)
If a subsurface is equal to or an ancestor of the parent surface we currently crash. Check for that case and terminate the client. Closes https://gitlab.gnome.org/GNOME/mutter/-/issues/1521 (cherry picked from commit 4e9a67acc6e09b012b6034b1928c2cc6ba0cb1bf)
Monitor tile info is possible to fetch when RANDR version 15 is exposed by the X11 server. We had inverted the check meaning that only if older versions were advertised would we attempt to init the tile information. Fix this guard, thus fix monitor tiling on X11. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1524 (cherry picked from commit 4ecc80fd8025842452262001fc4d6b7047696d4e)
As explained in https://gitlab.gnome.org/GNOME/mutter/-/issues/1494, with commit 29caa5bea576ed056aa6c82de192426abe6019ae we stopped queueing a relayout for the parent of the removed actor in clutter_actor_remove_child_internal(). This relayout was, as opposed to the relayout in clutter_actor_real_hide()/clutter_actor_real_unmap(), queued unconditionally without looking at the parents NO_LAYOUT flag. Now while that relayout in clutter_actor_remove_child_internal() would do unnecessary work if the parent had the NO_LAYOUT flag set, it did also queue a redraw of the parent, which is necessary in any case. So by removing that relayout in clutter_actor_remove_child_internal(), we stopped queueing redraws for NO_LAYOUT parents when a child gets removed from the scenegraph. This caused bugs where the texture of the child would be left visible on the screen even though the child got destroyed. To fix this, make sure again that we always queue a redraw on the parent when unmapping a child. Fixes https://gitlab.gnome.org/GNOME/mutter/-/issues/1494 (cherry picked from commit c88615aac869bf94a0e9ebc372396eabc640c0a3)
Not calling libinput dispatch in the backend constructor defeats the logic in post init as the device added events have not been processed yet. So instead of trying to guess the cursor initial visibility, simply update it along when devices get added. Additional benefit, we do not need to walk the all device list looking for touchscreens anymore, we just need to check the device being added since the current logic is to hide the cursor as soon as a touchscreen is found. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1534 (cherry picked from commit 9b881729821b360cc6e6f06f37fee0fe9b417a27)
At startup, libinput dispatch is called from the MetaSeatNative constructed callback. That means that we may get libinput events even before the default seat is set. In turn, processing those events may trigger the use the default seat while it's still not set yet, and cause a crash of gnome-shell/mutter at startup. A simple reproducer for this is to start gnome-shell/mutter with a tablet connected and the stylus in proximity, the proximity event will cause gnome-shell/mutter to crash at startup. To avoid that issue, avoid dispatching libinput events early from the MetaSeatNative constructed callback, those events will eventually get processed when the seat and the backend are all setup. https://gitlab.gnome.org/GNOME/mutter/-/issues/1501 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1534 (cherry picked from commit c618b8a0eb1919219da29934945b303fd0a311ed)