c436e7cb17
On a hybrid machine with i915 primary and nvidia-drm (470) secondary, `meta_render_device_egl_stream_initable_init` calls `meta_kms_inhibit_kernel_thread` to change from the default 'kernel' thread type to 'user'. And soon after that it would `meta_render_device_egl_stream_finalize` because I'm not actually using that GPU, and calls `meta_kms_uninhibit_kernel_thread`. So during startup Mutter would default to a realtime kernel thread, switch to a user thread (which doesn't support realtime), and then switch back to a realtime kernel thread. In the middle of all that, while the thread type was 'user' and realtime disabled, something was invoking `ensure_crtc_frame` which created a `CrtcFrame` without a deadline timer. Soon after that the thread type changed back to 'kernel' with deadline timers expected, but our existing `CrtcFrame` has no deadline timer associated with it. And so it would never fire, causing the cursor to freeze whenever the primary plane isn't changing. And the problem was permanent, not just the first frame because each `CrtcFrame` gets repeatedly reused (maybe shouldn't be called a "Frame"?). Now we adapt to switching between kernel and user thread types by adding and removing the deadline timer as required. Close: https://gitlab.gnome.org/GNOME/mutter/-/issues/3464 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3950> |
||
|---|---|---|
| .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/
- Cogl: https://mutter.gnome.org/cogl/
- CoglPango: https://mutter.gnome.org/cogl-pango/
- Mtk: https://mutter.gnome.org/mtk/
Meetings
There are recurring meetings to discuss development of GNOME Shell, mutter and related components.
License
Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.