Some devices can't scanout to linear buffers directly as the hw is not capable of eg rendering into a linear depth buffer. Add code to force kms-modifiers on udev taged devices. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1408 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1443
The X server, including Xwayland, can be compiled with different X11 extensions enabled at build time. When an X11 extension is built in the X server, it's usually also enabled at run time. Users can chose to disable those extensions at run time using the X server command line option "-extension". However, in the case of Xwayland, it is spawned automatically by the Wayland compositor, and the command line options are not configurable by users. Add a new setting to disable a selected set of X extension in Xwayland at startup, without needing to rebuild Xwayland. Of course, if Xwayland is not built with a given extension support in the first place (which is the default for the security extension for example), that option has no effect. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1405
Replace "whitelist" and "blacklist" with "allow_list" and "deny_list" which better represent the purpose of those variables. There is no functional change. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1396
The check-alive feature is there for the user to be able to terminate frozen applications more easily. However, sometimes applications are implemented in a way where they fail to be reply to ping requests in a timely manner, resulting in that, to the compositor, they are indistinguishable from clients that have frozen indefinitely. When using an application that has these issues, the GUI showed in response to the failure to respond to ping requests can become annoying, as it disrupts the visual presentation of the application. To allow users to work-around these issues, add a setting allowing them to configure the timeout waited until an application is considered frozen, or disabling the check completely. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1080
This replaces meta_should_autostart_x11_display(). The "on-demand" policy is not honored yet. https://gitlab.gnome.org/GNOME/mutter/merge_requests/709
We trigger the "locate-pointer" mechanism when a special key modifier (defaults to Control_L) key is pressed and released. https://gitlab.gnome.org/GNOME/mutter/merge_requests/453 https://gitlab.gnome.org/GNOME/gnome-shell/issues/981 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/merge_requests/19 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/86
To emulate X11 grabs, mutter as a Wayland compositor would disable its own keyboard shortcuts and when the X11 window is an override redirect window (which never receives focus), it also forces keyboard focus onto that X11 O-R window so that all keyboard events are routed to the window, just like an X11 server would. But that's a bit of a “all-or-nothing” approach which prevents applications that would legitimately grab the keyboard under X11 (like virtual machine viewers) to work by default. Change “xwayland-allow-grabs” to control whether the keyboard focus should be locked onto override redirect windows in case of an X11 grab. For stringent needs, careful users can still use the blacklisting feature (i.e. a list containing “!*”) to prevent grabs from any X11 applications to affect other Wayland native applications. https://gitlab.gnome.org/GNOME/mutter/issues/597
This is similar to a change in kwin: https://blog.martin-graesslin.com/blog/2017/09/kwinwayland-goes-real-time/ If the experimental features key has "rt-scheduler", make it claim the lowest of RT scheduler priorities, this will be both educated to other RT processes and improves responsiveness wrt all other processes. This can only work if mutter/gnome-shell process receives CAP_SYS_NICE somehow, e.g.: "setcap CAP_SYS_NICE=+ep `which gnome-shell`" Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/921 https://gitlab.gnome.org/GNOME/mutter/merge_requests/460
No need to redefine paths starting from top src/build dirs, as meson can give us this information for free using its functions. https://gitlab.gnome.org/GNOME/mutter/merge_requests/442
I saw Meson fade from the sky On the wind I heard a sigh As snowflakes cover fallen Makefiles I will say this last goodbye Meson is now coming So ends Autotools days Future is now coming And we must away Over Python and without Bashisms Through lands where never Meson touched By silver streams that run down to the Sea Under parsers, beneath old legacy Over snow one winter’s morn I turned at last to paths that lead home And though where the road then takes me I cannot tell We came all this way But now comes the day To bid you farewell Many places I have been Many sorrows I have seen But I don’t regret Nor will I forget All Makefiles that took that road with me I bid you all a very fond farewell.