76f689195e
meta_flush_input() creates and runs a main loop in order to block until the input thread has flushed all its events. This main loop is created on the default main context though (NULL is passed to g_main_loop_new()), which means that while the main loop runs, the default main context is active (aka stage updates will happen). This causes an issue with tests, specifically when there already is a stage update queued before running meta_flush_input(): meta_flush_input() will (as expected) block until the input thread flushed all its events to the main thread. But while that is happening, the main thread will be doing the stage update that was already queued, without the new events (the input thread is just starting to flush those). Then meta_flush_input() returns, and in our test we see that the stage has been updated, except it wasn't updated with the latest events. The test now continues and fails. To fix the issue, make meta_flush_input() truly blocking, so that it only flushes the input thread, but doesn't drive the global main context while waiting for that. After the flushing is finished, tests must now manually iterate the main context themselves to ensure that a stage update happens. This breaks a few stacking tests, because "move_cursor_to" and "click" use meta_flush_input() internally. For those commands we now need to dispatch a stage update afterwards. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3807> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| clutter | ||
| cogl | ||
| data | ||
| doc | ||
| meson | ||
| mtk | ||
| po | ||
| src | ||
| subprojects | ||
| tools | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| check-style.py | ||
| config.h.meson | ||
| COPYING | ||
| logo.svg | ||
| meson.build | ||
| meson_options.txt | ||
| mutter.doap | ||
| NEWS | ||
| README.md | ||
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 first look at the GNOME Handbook and the documentation and API references below first.
Documentation
- Coding style and conventions
- Git conventions
- Code overview
- Building and Running
- Debugging
- Monitor configuration
API Reference
- Meta: https://mutter.gnome.org/meta/
- Clutter: https://mutter.gnome.org/clutter/
- Cally: https://mutter.gnome.org/cally/
- Cogl: https://mutter.gnome.org/cogl/
- CoglPango: https://mutter.gnome.org/cogl-pango/
- Mtk: https://mutter.gnome.org/mtk/
License
Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.