c41657bc4f
When an activation times out, we'll be signalled two signals on the startup sequence object: "timeout", and "complete". Normally, the "complete" signal is emitted when a startup sequence is completed succesfully by it being used for activation, and in this case, the xdg_activation implementation should remove the sequence from the startup notification machinery. However, in the timeout case, we should not remove it, as the startup notification machinery itself will deal with this. If we would, we'd end up with use-after-free issues, as the sequence would be finalized when removed the first time. To avoid this, just clean up the Wayland side in the "timeout" signal handler, leaving the "complete" signal handler early out if it was already handled by it. This avoids crashes like: 0) g_type_check_instance (type_instance=type_instance@entry=0xdd6740) 1) g_signal_handlers_disconnect_matched (instance=0xdd6740, ...) 2) meta_startup_notification_remove_sequence (sn=0x4cc890, seq=0xdd6740) at ../src/core/startup-notification.c:544 3) startup_sequence_timeout (data=0x4cc890, ...) at ../src/core/startup-notification.c:504 4) g_timeout_dispatch (...) at ../glib/gmain.c:4933 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2081> |
||
---|---|---|
.gitlab/issue_templates | ||
.gitlab-ci | ||
clutter | ||
cogl | ||
data | ||
doc | ||
meson | ||
po | ||
src | ||
subprojects | ||
tools | ||
.gitignore | ||
.gitlab-ci.yml | ||
check-style.py | ||
config.h.meson | ||
COPYING | ||
HACKING.md | ||
meson_options.txt | ||
meson.build | ||
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 af 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.
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.
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.