Go to file
Carlos Garnacho 630f13db78 x11: Handle ConfigureRequest events in frames
Under strange timings, the GTK frames client may implicitly queue
relayouts that end up disagreeing with the latest frame size as
given by Mutter, this results in GTK calling XResizeWindow, and
Mutter plain out ignoring the resulting XConfigureRequestEvent
received.

This however makes GTK think there's pending resize operations,
so at the next resize it will freeze the window, until enough
resizes happened to thaw it again. This is seen as temporary
loss of frame-sync ness (e.g. frozen frame, and other weird
behavior).

In order to make GTK happy and balanced, reply to this
XConfigureRequest, even if just to ignore it in a more polite
way (we simply re-apply the size Mutter thinks the frame should
have, not GTK), this results in the right amount of
ConfigureNotify received on the frames client side, and the
surface to be thawed more timely, while enforcing the size as
managed by Mutter.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2837
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3189>
2023-08-31 20:53:04 +00:00
.gitlab/issue_templates gitlab: Add missing < in markdown comment tag 2020-02-14 03:10:28 +00:00
.gitlab-ci ci: Look for matching ref in user remote for branch pipeline 2023-08-08 04:11:13 +02:00
clutter Remove unused *.pc.in 2023-08-31 09:47:50 +00:00
cogl Remove unused *.pc.in 2023-08-31 09:47:50 +00:00
data remote-desktop/eis: Add support for ConnectToEIS. 2023-07-14 22:23:45 +00:00
doc build: Add a Meta Toolkit private library 2023-08-30 16:46:13 +02:00
meson build: Replace custom post-install script 2022-11-19 02:21:05 +01:00
mtk mtk: Move Rectangle.from_graphene_rect from Meta 2023-08-30 16:46:14 +02:00
po Update Lithuanian translation 2023-08-31 20:20:48 +00:00
src x11: Handle ConfigureRequest events in frames 2023-08-31 20:53:04 +00:00
subprojects build: Update sysprof build options 2022-12-17 19:58:00 +00:00
tools tools/get-state: Round refresh rates to three decimal places 2022-08-19 15:28:56 +00:00
.gitignore Add .buildconfig to .gitignore 2023-02-17 21:44:29 +00:00
.gitlab-ci.yml build: Add a Meta Toolkit private library 2023-08-30 16:46:13 +02:00
check-style.py check-style: Allow deciding on individual suggestions with --rewrite 2023-02-20 22:21:01 +00:00
config.h.meson edid: Integrate libdisplay-info for edid parsing 2023-05-02 17:37:01 +00:00
COPYING Updated obsolete FSF postal address in COPYING 2014-01-12 08:44:30 +07:00
HACKING.md docs: Update coding style link 2021-11-09 19:52:14 +01:00
meson_options.txt edid: Integrate libdisplay-info for edid parsing 2023-05-02 17:37:01 +00:00
meson.build build: Add a Meta Toolkit private library 2023-08-30 16:46:13 +02:00
mutter.doap mutter.doap: Add marge-bot as a maintainer 2020-11-16 11:59:45 +01:00
NEWS cleanup: Fix various typos 2023-08-12 20:13:37 +00:00
README.md readme: Expand how to tag commit messages 2023-03-03 23:17:26 +00:00

Mutter

Mutter is a Wayland display server and X11 window manager and compositor library.

When used as a Wayland display server, it runs on top of KMS and libinput. It implements the compositor side of the Wayland core protocol as well as various protocol extensions. It also has functionality related to running X11 applications using Xwayland.

When used on top of Xorg it acts as a X11 window manager and compositing manager.

It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.

Internally it uses a fork of Cogl, a hardware acceleration abstraction library used to simplify usage of OpenGL pipelines, as well as a fork of Clutter, a scene graph and user interface toolkit.

Mutter is used by, for example, GNOME Shell, the GNOME core user interface, and by Gala, elementary OS's window manager. It can also be run standalone, using the command "mutter", but just running plain mutter is only intended for debugging purposes.

Contributing

To contribute, open merge requests at https://gitlab.gnome.org/GNOME/mutter.

It can be useful to look at the documentation available at the Wiki.

The API documentation is available at:

Coding style and conventions

See HACKING.md.

Git messages

Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit. Try to always prefix commit subjects with a relevant topic, such as compositor: or clutter/actor:, and it's always better to write too much in the commit message body than too little.

If a commit fixes an issue and that issue should be closed, add URL to it in the bottom of the commit message and prefix with Closes:.

Do not add any Part-of: line, as that will be handled automatically when merging.

The Fixes tag

If a commit fixes a regression caused by a particular commit, it can be marked with the Fixes: tag. To produce such a tag, use

git show -s --pretty='format:Fixes: %h (\"%s\")' <COMMIT>

or create an alias

git config --global alias.fixes "show -s --pretty='format:Fixes: %h (\"%s\")'"

and then use

git fixes <COMMIT>

Example

compositor: Also consider dark matter when calculating paint volume

Ignoring dark matter when calculating the paint volume missed the case where
compositing happens in complete vacuum.

Fixes: 123abc123ab ("compositor: Calculate paint volume ourselves")
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1234

Default branch

The default development branch is main. If you still have a local checkout under the old name, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main

License

Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.