commit b2958a33cba90f27fc44062f665a1913268a319a
Author: Simon McVittie <smcv@debian.org>
Date: Mon Feb 16 21:57:03 2026 +0000
Update changelog
commit c5db3682c88c41e85fc6bef5b7d70a18450e78c0
Merge: e8624c1c 491b0863
Author: Simon McVittie <smcv@debian.org>
Date: Mon Feb 16 21:56:29 2026 +0000
Merge branch 'debian/forky' into debian/latest
commit 491b08631fab3a220ecba83d972f39a26fc04e51
Author: Simon McVittie <smcv@debian.org>
Date: Mon Feb 16 20:00:44 2026 +0000
Release to unstable
commit 8534528a19d6abcaf595455c48cadb7c9d4f50d1
Author: Simon McVittie <smcv@debian.org>
Date: Sun Feb 15 17:21:15 2026 +0000
Update changelog
commit 8c33a8795f095e24aaa0c5da954d550cd66907b1
Author: Simon McVittie <smcv@debian.org>
Date: Sun Feb 15 17:20:23 2026 +0000
d/libmutter-17-0.symbols: Update
commit d6e94ec8f1dab55fd4e44a6fda8a4ad7a157a0fa
Author: Simon McVittie <smcv@debian.org>
Date: Sun Feb 15 17:12:16 2026 +0000
New upstream release
commit ce9e04ca847ab8f00255e1e5174174aae22ab37a
Merge: 2dba0ac0 658345be
Author: Simon McVittie <smcv@debian.org>
Date: Sun Feb 15 17:12:16 2026 +0000
Update upstream source from tag 'upstream/49.4'
Update to upstream version '49.4'
with Debian dir c9e625239f13abd0a8b31e0195963a29dcdd3663
commit 658345beb9ef4c5f53e9d7c3e2170c06f35fd882
Merge: 4f53b444 e6379ecf
Author: Simon McVittie <smcv@debian.org>
Date: Sun Feb 15 17:12:02 2026 +0000
New upstream version 49.4
commit e6379ecf07e7962d796fc057c50d0e6b2d803b7e
Author: Florian Müllner <fmuellner@gnome.org>
Date: Thu Feb 5 16:47:05 2026 +0100
Bump version to 49.4
Update NEWS.
commit d2b8e1bb922113bf29d11a2f002a5ece16196025
Author: Carlos Garnacho <carlosg@gnome.org>
Date: Thu Feb 5 15:40:14 2026 +0100
wayland: Fix possible invalid reads when terminating popup grabs
There is a bit of an egg-and-chicken problem between a popup grab,
and the surfaces it applies to. Finishing a grab will iterate through
all popups, and free the MetaWaylandPopupGrab struct on the last one,
while the MetaWaylandPopupGrab list of popup surfaces is being iterated.
In order to fix the possible invalid reads (and crashes) resulting from
this, hook into the return value of meta_wayland_popup_surface_finish()
to know we should break the loop.
While at it, also move another place to using this return value, as
it's checking for the same preconditions as the ::finish() implementation
underneath.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4886>
(cherry picked from commit d5981ff119402b420c61a8302aa3f0e87805284c)
commit dbfa2d19c881101a8568d97294eb390d6bf19157
Author: Carlos Garnacho <carlosg@gnome.org>
Date: Thu Feb 5 15:38:24 2026 +0100
wayland: Notify grab finish from MetaWaylandPopupSurfaceInterface::finish
Return a boolean value, expressing whether the grab was terminated together
with the popup surface, or whether no action was taken.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4886>
(cherry picked from commit b6a5aff28e47c624670881a67fdd2668942d55d9)
commit 77de39e3f706dba6c03408f54b2a3ce02ddc2253
Author: Jonas Ådahl <jadahl@gmail.com>
Date: Fri Oct 10 10:08:05 2025 +0200
wayland/popup: Handle popups dismissing other popups when finishing
We'd dismiss all popups in the list, but didn't handle the case where
one popup indirectly dismissed another, meaning we'd dismissing it
again, after it was freed. Handle this by going through the list only
looking at the first element, until it's empty.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4843>
(cherry picked from commit 503e9d93aecf8a3d95a28eb410b883aeaae942ee)
commit 8fee00136259be8e1fc93496e4656ca2de3c105d
Author: Jonas Ådahl <jadahl@gmail.com>
Date: Tue Dec 9 16:43:49 2025 +0100
screen-cast-stream-src: Log negotiated dimension and framerate
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4881>
commit 7bc3df0e740b0594a188142e81705b81d8bbbf21
Author: Jonas Ådahl <jadahl@gmail.com>
Date: Tue Dec 9 16:42:25 2025 +0100
screen-cast-stream-src: Only specify framerate range if there is any
When recording a monitor with no set refresh rate, don't set the
maxFramerate parameter, as that may confuse negotiation. More precisely,
a rate of 0/1 is considered zero, which is smaller than e.g. 60/1, but
shouldn't be considered as such.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4881>
commit 6d02b355b1c6ad045689e76e4b27ab4f3a3b9ea7
Author: Jonas Ådahl <jadahl@gmail.com>
Date: Tue Dec 9 16:39:34 2025 +0100
screen-cast-stream-src: Set framerate params in push_format_object()
The framerate is always the same (variable), so only specify the range.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4881>
commit e25569e1bb9bb8c9ed8377027f03e5be3cb930ba
Author: Sebastian Keller <skeller@gnome.org>
Date: Tue Jan 27 17:24:48 2026 +0100
backends: Clarify meta_idle_monitor_add_idle_watch() documentation
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4422>
(cherry picked from commit f8ae5b4732a4167402e321b94f0b98a83b631e5c)
commit dc5b818fc94ac04b5052237e224293f3e6bdc426
Author: Sebastian Keller <skeller@gnome.org>
Date: Fri Jan 23 19:19:15 2026 +0100
backends: Allow ignoring previous idle time when creating idle watches
This is useful for things like break reminders that need to know that a
user has been idle for a specified time from when the reminder was
triggered rather than from when the user was idle. The user might have
been watching a video which would have counted to the previous idle time
if the watcher ignores inhibitors.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4422>
(cherry picked from commit 3f3bea1d4a6f2cfd99f4c2b4ceaf316eeaed6059)
commit d075bf68975a9e5b2bacd88bf8c4dd7135cb0e96
Author: Sebastian Keller <skeller@gnome.org>
Date: Tue May 6 01:23:05 2025 +0200
backends: Allow creating uninhibitable idle watches
Some idle watches are really only interested in whether there is user
activity, but not if there are any inhibiting clients. An example for
this would be the break timer in gnome-shell which should not be
affected by inhibitors.
Related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8378
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4422>
(cherry picked from commit 02c1c9edeab5f16ca2e7b499e98380b0cf31b93f)
commit ba4c9b488168d816ea904cb90539b371aae283d1
Author: mohansur <MohanSundaram.R@amd.com>
Date: Tue Feb 3 11:07:26 2026 +0530
window: Remove obsolete fullscreen coverage check for O-R windows
Fullscreen coverage check for override-redirect windows queued from
meta_window_constructed() are no longer needed now that the check is
queued after update_top_window_actor()
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4876>
(cherry picked from commit e55185439b718b3b6922d7ab591d4144a87dc997)
commit ddcd3fdcffa9bc962b10644d25c57ffc2d9b5492
Author: mohansur <MohanSundaram.R@amd.com>
Date: Sat Jan 31 19:30:04 2026 +0530
compositor: Queue for fullscreen check after updating top window actor
A regression introduced in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4820 caused fullscreen coverage
checks to run with an out-of-date top window actors.
A fullscreen check after updating top window actor would rectify this.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/4571
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4876>
(cherry picked from commit 8e6156c0c7b43d1e373b9717eb829ec639f17dc8)
commit 379da7870f6815cc869bea742d7c4a5ab613845b
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Sat Feb 7 12:10:19 2026 +0100
clutter/color-state-params: Disable tone mapping with HDR on for now
The current tone mapping implementation doesn't work correctly with
the current blending colour space. Luminance mapping would need to be
handled separately from the actual tone mapping.
Tone mapping with HDR on doesn't really make sense anyway while we're
always using the full PQ luminance range up to 10000 nits, which no real
display can actually reproduce.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/4591
(Cherry picked from commit c3a5809c55442d0dcbf8c7d1623be491af46ccc7)
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4902>
commit 84e5433bd4b05f3a3f5f4913211afaa2f5f40c4b
Author: Daniel Rusek <mail@asciiwolf.com>
Date: Wed Feb 4 23:20:40 2026 +0000
Update Czech translation
commit 7a74e7c7bf53f608be6ab4b07fce0b0ad1aecc4a
Author: Robert Mader <robert.mader@collabora.com>
Date: Mon Feb 2 15:49:43 2026 +0100
clutter/color-state-params: Clamp BT1886 input values
In line with the PQ shaders. This fixes artifacs/banding issues, making
the output visually match that of Mesa GL/VK shaders or display engines
much closer.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4878>
(cherry picked from commit 0135cce6db41c4775f6e54750d65a8188bafc794)
commit 0dcaa45a225cedc8207158f1e049ed3f023a4469
Author: Andika Triwidada <atriwidada@gnome.org>
Date: Fri Jan 23 12:02:48 2026 +0000
Update Indonesian translation
commit b5486113116924a2685ec41ff84221bdbc2c47b5
Author: Antonio Marin <gnmer.6qxyg@slmail.me>
Date: Thu Jan 22 10:38:50 2026 +0000
Update Romanian translation
commit d2a08421d1eba9f476202746b1b73f88433dba1f
Author: mohansur <MohanSundaram.R@amd.com>
Date: Mon Jan 5 23:02:03 2026 +0530
x11: Apply scaling property during initial monitor config commit
Apply scaling during initial xrandr apply monitors config
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/4484
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4834>
Among the 5 debian patches available in version 49.4-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/mutter.png){kind=link}