Commits on Source (26)
-
Kjartan Maraas authored87cb57f2
-
Juliano de Souza Camargo authored2d69e27a
-
Florentina Mușat authored1830486d
-
Aleksandr Mezin authored
To find XWayland output that should be the primary one, iterate through all XWayland outputs, and compare their geometry to the geometry of the primary logical monitor. To avoid possible race conditions (Mutter's monitor configuration already updated, but Xrandr not yet), set the output both after Randr notifications and after 'monitors-changed' signal. https://gitlab.gnome.org/GNOME/mutter/-/issues/1407 Signed-off-by: Aleksandr Mezin <mezin.alexander@gmail.com> (cherry picked from commit 4f544b63) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1638>
00e247ed -
Olivier Fourdan authored
The function focus_default_window() optionally takes a MetaWindow argument denoting a window that should not be focused. That function calls focus_ancestor_or_top_window() which in turn calls meta_window_focus() to pass focus to another window. However meta_window_focus() gives no guarantee that the given window will end up being the one focused, and can fail in various and creative ways. If that fails, we could possibly end up with the focus window being the one to avoid, while the caller assumes focus was changed, going as far as asserting that fact like meta_window_unmanage() does. As a result, mutter may abort simply because meta_window_focus() failed to set focus on the expected window. To avoid that issue, check that the focus did not end up on the window that we explicitly did not want, and if that's the case, simply fallback to the default focus window. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/862 (cherry picked from commit afa43154) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1650>
e4d8e4b9 -
Olivier Fourdan authored
find_focusable_ancestor() may pick an ancestor window which is not mapped or hidden, and setting focus on that window will fail. Be a tad more selective when looking for a focusable ancestor, to reduce the chance of meta_window_focus() not focusing the happy chosen one. (cherry picked from commit 76d1a642) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1650>
5fab0e10 -
Jonas Ådahl authored
This adds a test case for https://gitlab.gnome.org/GNOME/mutter/-/issues/862 that checks that hiding a dialog where its parent is not yet shown doesn't trigger any asserts or crashes. (cherry picked from commit c94d9293) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1650>
fbb9a34f -
Extract some boilerplate into new functions for next patch. No functional change intended. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561> (cherry-picked from commit 45a9c386)
c05815f8 -
After last monitor gets unplugged from the system, hotplug detection may no longer work on Intel GFX. This is because we didn't trigger a modeset to disable CRTCs, and i915 requires it to make hotplug detection continue to work [1]. Ensure disabled CRTCs are unset and post a modeset to disable them. [1] https://www.kernel.org/doc/html/latest/gpu/i915.html#hotplug https://gitlab.freedesktop.org/drm/intel/-/issues/2602 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561> (cherry-picked from commit e5b07138)
ed1ab1e4 -
After last monitor gets unplugged from the system, hotplug detection may no longer work on Intel GFX. This is because we didn't trigger a modeset to disable CRTCs, and i915 requires it to make hotplug detection continue to work [1]. There's no guarantee that DPMS off in DDX also disables CRTCs, so explicitly disable CRTCs to solve the issue. [1] https://www.kernel.org/doc/html/latest/gpu/i915.html#hotplug https://gitlab.freedesktop.org/drm/intel/-/issues/2602 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561> (cherry-picked from commit ed87937f)
d29a0f4c -
Marc-Antoine Perennou authored
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1668> (cherry picked from commit d439501f)
feb11d99 -
Changes in games between fullscreen and windowed modes may trigger chaotic situations where the buffer and the frame size temporarily disagree, producing rectangles with negative width/height. This is usually followed by other updates that bring the pointer constraint up to date. This makes cairo panic and return an "error" empty region, which breaks deeper down when using the region rectangles to apply the pointer constraint. If we hit this situation, ignore the frame rectangle, and just go with the buffer rectangle. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1655> (cherry picked from commit 98ef6d0d)
429491c7 -
Florian Müllner authored
Update NEWS.
9f9c26be -
Simon McVittie authorede3d8660c
-
Simon McVittie authored2e0a4391
-
Simon McVittie authored0db78113
-
Simon McVittie authored
Update to upstream version '3.38.3' with Debian dir 44a93177ca283e17dd816bcf86ff27d2d1311ca1
f5a89e0e -
Simon McVittie authored7742b4c2
-
Simon McVittie authoredffa40fe2
-
Simon McVittie authored5d6c8bbf
-
Simon McVittie authored
- Cope with monitors with metacharacters in their EDID data - Don't crash if parsing monitor configuration fails - Don't crash if an extension tries to add the same window to a workspace more than once, such as auto-move-windows - Cope with monitor configuration changes during screencasting - Speed up workspace switching when many windows are open - Fix Xwayland windows not always appearing in the gnome-shell overview - Avoid warning spam and poor performance when unmanaging a window (Closes: #970295, LP: #1841774)
3ee439e9 -
Simon McVittie authored6414ff10
-
Marco Trevisan authored
mutter release 3.38.3-2 for unstable (sid) (maintainer view tag generated by dgit --quilt=unapplied) [dgit distro=debian split --quilt=unapplied]
fa8458f9 -
Marco Trevisan authoredbcda8d6e
-
Marco Trevisan authoredce2ac1f3
-
Marco Trevisan authored2766d242
This diff is collapsed.