| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| x11-events-NULL-Check-input-event-when-getting-name.patch | x11/events: NULL Check input event when getting name Fixes a SIGSEGV when trying to get the name of an XIEvent for profile trace data gathering. We don't use GDK anymore, so we can't rely on any GDK semantics. |
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> | yes | upstream, 45.alpha, commit:33a210d768c7e29011e4e97e4eaf9356a7efb303 | 2023-05-10 | |
| workspace-Don-t-crash-on-invalid-argument-to-meta_workspa.patch | workspace: Don't crash on invalid argument to meta_workspace_index This is no longer strictly necessary after #2559 was fixed in 44.beta, but could add some extra robustness by turning a crash into a somewhat graceful check failure. this until we upgrade to a version that includes it; but if the upstream merge request is rejected, we should drop this. |
Simon McVittie <smcv@debian.org> | yes | debian upstream | 2022-12-18 | |
| workarounds/tests-Mark-view-verification-tests-as-incomplete-in-big-e.patch | tests: Mark view-verification tests as incomplete in big-endian archs Saved pixmaps are invalid in big-endian architectures, so let's disable the tests for now, checking only the basic metadata but not comparing the contents. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | 2021-06-15 | |
| debian/meson-Do-not-mark-CI-test-tools-as-required.patch | meson: Do not mark CI test tools as required This way we can mark them as nocheck without build issues. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2022-02-18 | ||
| debian/tests-Do-not-run-screencast-tests.patch | tests: Do not run screencast tests They require to have a full running pipewire (that requires a system dbus daemon) so, we can't easily get one up and running while building. So let's disable this for now |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2021-05-20 | ||
| workarounds/tests-skip-monitor-width-size-check-as-it-may-lead-to-une.patch | tests: skip monitor width size check as it may lead to unexpected failure This seems to be broken only on autopkg-tests. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | not-needed | 2022-03-14 | ||
| workarounds/wayland-data-device-Allow-any-drag-timestamp-as-drag-star.patch | wayland-data-device: Allow any drag timestamp as drag start serial In some scenarios under wayland DnD may not work because the start-drag serial is not matching the one we expect for the pointer that we set when handling the button event. This is because since commit 26676a82 we're repeatedly pinging the windows at each event to ensure that they're still alive, but we're using the event timestamp for that, and this makes wayland to use such value as the start-drag serial. To avoid this, let's keep track of all the grab timestamps we got while dragging and accept a serial to match any of these. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | 2022-04-06 | |
| debian/Support-Dynamic-triple-double-buffering.patch | Support Dynamic triple/double buffering Use triple buffering if and when the previous frame is running late. This means the next frame will be dispatched on time instead of also starting late. It also triggers a GPU clock boost if deemed necessary by the driver. Although frequency scaling is not required to get a performance gain here because even a fixed frequency GPU will benefit from not over-sleeping anymore. If the previous frame is not running late then we stick to double buffering so there's no latency penalty when the system is able to maintain full frame rate. Formatted for Debian (as of 44.3) with: git remote add vanvugt git@ssh.gitlab.gnome.org:vanvugt/mutter.git git fetch vanvugt git merge --squash -e vanvugt/triple-buffering-v4-44 And then git commit but using all this as the header instead of what git suggests. Also add Gbp-Pq: Topic debian |
Daniel van Vugt <daniel.van.vugt@canonical.com> | yes | upstream | 2023-08-14 | |
| build-Support-sysprof-6.patch | build: Support sysprof-6 Sysprof 45 changed the API version of the main library. We mainly depend on sysprof-capture which is *not* affected, except for looking up the datadir where sysprof's D-Bus interfaces are installed. That lookup doesn't care whether we are using sysprof-6 or sysprof-4, so accept either dependency. https://gitlab.gnome.org/GNOME/mutter/-/issues/2962 |
=?utf-8?q?Florian_M=C3=BCllner?= <fmuellner@gnome.org> | no | https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3187 | 2023-08-16 | |
| workarounds/Mark-several-additional-tests-as-flaky.patch | Mark several additional tests as flaky Most of these have never been reliable on Debian buildds, especially on ARM, so having them fail is not a regression. They usually succeed after a few retries, but that's time-consuming and unsuitable to be a QA gate. |
Simon McVittie <smcv@debian.org> | no | 2023-12-13 | ||
| ibus-caps-lock-accented-letters.patch | backends/native: Translate keycodes with xkb_key_state_get_one_sym() There's two aspects from its documentation (https://xkbcommon.org/doc/current/group__state.html#gae56031a8c1d48e7802da32f5f39f5738) affecting us here: 1. "This function is similar to xkb_state_key_get_syms(), but intended for users which cannot or do not want to handle the case where multiple keysyms are returned (in which case this function is preferred)." We are indeed in that field, and have been for a long time. 2. "This function performs Capitalization Keysym Transformations." This is unlike the xkb_key_get_syms() function that we use, and convenient here for parity with X11 since it behaves exactly that way. Fixes cases where the keysym for some keys is not properly capitalized when caps lock is toggled, due to the output of capslock+key being different from shift+key. An example of this is 'é' in french(azerty) layout (bound to the '2' key). Even though shift+2 outputs '2', capslock+é should output 'É'. (cherry picked from commit 6fe1b3145f840d39240046c0812b1406d23fe569) |
Carlos Garnacho <carlosg@gnome.org> | no | 45.1 | 2023-09-29 | |
| backends-Use-standard-cursor-names-from-the-CSS-specifica.patch | backends: Use standard cursor names from the CSS specification This is the preferred name set, and handled by adwaita icon theme. Use the names from https://www.w3.org/TR/css-ui-4/#cursor, like GDK does at https://docs.gtk.org/gdk4/ctor.Cursor.new_from_name.html. (cherry picked from commit d970c9db1abdb0e1f26aeff43518265471ba303b) |
Carlos Garnacho <carlosg@gnome.org> | no | 46.alpha | 2023-09-22 | |
| backends-Attempt-a-fallback-to-default-cursor-on-failed-l.patch | backends: Attempt a fallback to 'default' cursor on failed lookups While we should ideally have a sensible cursor theme, handle the case of cursor themes that lack certain cursor names, and fallback to the 'default' cursor in those cases. The 'grey rectangle' fallback is still left, in case we even fail to load a 'default' cursor. (cherry picked from commit 9f89421ef5abfe5143a777aa33eee308e81a7055) |
Carlos Garnacho <carlosg@gnome.org> | no | 46.alpha | 2023-10-03 | |
| backends-Update-cursor-names-to-match-updated-metaphors.patch | backends: Update cursor names to match updated metaphors adwaita-icon-theme updated its cursor metaphors and changed all DnD cursors to use arrows instead of hands, except for the grab related ones. Mutter was using "grabbing" as default DnD cursor, which now does not match the other DnD cursors ("copy" and "no-drop") anymore. Change this to the "default" cursor. Additionally, because the "no-drop" cursor now puts a stronger emphasis on the crossed out symbol also prefer "default" for META_CURSOR_DND_IN_DRAG and only use "no-drop" for things that explicitly don't accept a drop. (cherry picked from commit f99c6badb95309e47e019d3622c9db5dd559da30) |
Sebastian Keller <skeller@gnome.org> | no | 46.beta | 2024-01-17 |