Debian Patches

Status for mutter/49.0-3

Patch Description Author Forwarded Bugs Origin Last update
Use-dbus-debug-topic-for-D-Bus-name-changes.patch Use 'dbus' debug topic for D-Bus name changes
Lets make it a META_DEBUG_DBUS debug log entry instead. It's not useful
to have in the journal, and it interferes with tests trying to assert
that expected warnings are logged.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-09
wayland-xdg-shell-Make-invalid-geometry-warning-more-desc.patch wayland/xdg-shell: Make invalid geometry warning more descriptive
It'll contain app id and window title, if available.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-10
tests-wayland-Add-test-case-for-client-with-invalid-geome.patch tests/wayland: Add test case for client with invalid geometry
This makes sure we gracefully handle a client providing an invalid
window geometry.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-10
wayland-surface-Make-state-applied-logs-more-informative.patch wayland/surface: Make state-applied logs more informative
Include the new surface size, i.e. log about applying a bit later, after
any buffer or viewport state has been applied.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-11
wayland-shell-surface-Assume-geometry-empty-if-no-buffer-.patch wayland/shell-surface: Assume geometry empty if no buffer attached
Don't include subsurfaces when deriving the actual window geometry if
the main surface isn't yet mapped, since subsurfaces are not mapped if
the parent surface isn't, which it can't be unless there is a buffer
attached.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-11
wayland-xdg-shell-Ensure-applied-window-geometry-is-alway.patch wayland/xdg-shell: Ensure applied window geometry is always non-empty

Well behaved clients will never end up with a empty window geometry, but
buggy ones could, so to not have to handle that in generic window
management code, try harder to work around broken Wayland client
behavior in Wayland code by be more forgiving when it comes to fix up
incorrectly configured window geometry.

While this will paper over bad client behavior, it'll allow the window
management code remaining ignorent about such awkwardness. Effort is
made to log offending clients to the journal so developers are
potentially made aware of it.

This also makes the window positioning of surfaces with this type of
invalid state more predictable, so update the test case accordingly.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-11
tests-wayland-Add-test-for-invalid-geometry-with-subsurfa.patch tests/wayland: Add test for invalid geometry with subsurface
This imitates invalid Wayland protocol semantics seen done by a client
that temporarily maps subsurfaces, setting a window geometry when
creating and destroying said subsurfaces, but then when finally
committing the buffer not accompanying that commit with a new window
geometry.
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> yes upstream 2025-09-11
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
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/tests-Skip-thread-priority-test.patch tests: Skip thread priority test
This test added to 45 fails on Ubuntu's armhf builders

https://launchpad.net/ubuntu/+source/mutter/45~beta.1-0ubuntu1/+latestbuild/armhf

and on Debian's i386

https://buildd.debian.org/status/logs.php?pkg=mutter&arch=i386

Architecture defines are at
https://wiki.debian.org/ArchitectureSpecificsMemo
=?utf-8?q?Jeremy_B=C3=ADcha?= <jeremy.bicha@canonical.com> no 2023-08-21
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.

The input-capture test frequently hangs until it times out, so put that
one in a separate suite so that we don't need to run it at all.
Simon McVittie <smcv@debian.org> no 2023-12-13
workarounds/tests-Install-stacking-tests-into-a-subdirectory.patch tests: Install stacking tests into a subdirectory
These are not reliable enough on ci.debian.net to be used as a QA gate.
Simon McVittie <smcv@debian.org> not-needed debian 2024-09-07

All known versions for source package 'mutter'

Links