| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| wayland-subsurface-Check-for-parent-actor-before-unparent.patch | wayland/subsurface: Check for parent actor before unparenting No need to assume the actor still has a parent. This silences warnings in normal builds and prevents a crash in fully optimized ones. |
Robert Mader <robert.mader@posteo.de> | yes | upstream | upstream, 3.38.7, commit:0db4ac7373965011a0fb2d3ff0465c227333d4c3 | 2021-08-06 |
| wayland-subsurface-Handle-node-unlinking-on-parent-destro.patch | wayland/subsurface: Handle node unlinking on parent destroyed It concerns subsurface state and the subsurface already listenes for the parent to get destroyed. |
Robert Mader <robert.mader@posteo.de> | yes | upstream | upstream, 3.38.7, commit:60afd63ef581b11b7cd8483d4a83ce24480ed8e8 | 2021-08-06 |
| debian/tests-Tag-unstable-tests-as-flaky.patch | tests: Tag unstable tests as flaky Then test runners can run these ones non-fatally. This is Debian-only: for upstream these tests should be fixed. |
Iain Lane <iainl@gnome.org> | not-needed | 2019-08-14 | ||
| window-actor-wayland-Remove-subsurface-actors-on-dispose.patch | window-actor/wayland: Remove subsurface actors on dispose Destroying the window actor also destroys all its children. Subsurfaces however may get reused. If the client did not unparent them before the window actor got destroyed, they will be left without actor which results in a crash. Unparent all actors of subsurfaces on dispose to avoid that. |
Robert Mader <robert.mader@posteo.de> | yes | upstream | upstream, 3.38.7, commit:58343f43dfee81a7b2791a37c610b5e27557fd6f | 2021-08-06 |
| xwayland-Fix-condition-for-queuing-a-window-to-META_QUEUE.patch | xwayland: Fix condition for queuing a window to META_QUEUE_CALC_SHOWING This logic was changed by accident in df642eb15. The change caused every Xwayland window to be queued to META_QUEUE_CALC_SHOWING on every surface commit. As a result, X11 window management events, including _NET_WM_STATE, were dispatched at clients on every single frame. (cherry picked from commit 98d5aa159e0eb9f433b211044ce30cd612d42734) |
Dor Askayo <dor.askayo@gmail.com> | yes | upstream | upstream, 3.38.7, commit:bb85f21d1f0c7ff7d65fc4a89f41c9fed6025f05 | 2021-10-01 |
| wayland-data-offer-Accept-final-preferrence-of-drop-desti.patch | wayland/data-offer: Accept final preferrence of drop destination Quoting the spec for `wl_data_device::drop`: > If the resulting action is "ask", the action will not be considered > final. The drag-and-drop destination is expected to perform one last > wl_data_offer.set_actions request, or wl_data_offer.destroy in order > to cancel the operation. We did not respect the action choosen by the drop destination when it called `wl_data_offer::set_actions` after `wl_data_device::drop` if a user override was still active. This eventually resulted in a protocol error in `wl_data_offer::finish`, as the current action could still be `ask`. Fix this by only allowing a user override to `ask` before `drop` is called, thus making sure the final `set_actions` preference is honored. (cherry picked from commit 33b834c43373b715219d1b911813b59b2d0e2477) |
Robert Mader <robert.mader@posteo.de> | yes | upstream | upstream, 3.38.7, commit:5a6b3c4b67f2c07d4497e955f4a85a1a11474ca1 | 2021-10-06 |
| surface-actor-Fix-unobscurred_fraction-calculation.patch | surface-actor: Fix unobscurred_fraction calculation This calculation wrongly applied a `x2 - x1` pattern. (cherry picked from commit 6204769fdb8a048ee23f49be0ca532f8ff1d557a) |
Robert Mader <robert.mader@posteo.de> | yes | upstream | upstream, 3.38.7, commit:15ac84da2da518850e9c247b81d23becad223195 | 2021-12-19 |
| wayland-surface-Switch-order-for-calculating-surface-dama.patch | wayland/surface: Switch order for calculating surface damage Process surface damage in the right order, simplifying the calculations. No functional change intended. (cherry picked from commit f4717d0ac51625d271f3a8cdc6804fa9461bc927) |
Robert Mader <robert.mader@collabora.com> | no | upstream, 3.38.7, commit:a9e60badaf5e0ef98a3669298b278cc9a3cb9dfc | 2021-12-18 | |
| debian/synaptics-support.patch | backends/x11: Support input-synaptics, if present. Add support for configuring the Xorg synaptics touchpad driver. Turns out it's very simple to support both libinput and synaptics simultaneously, both under the heading of XI2. |
Daniel van Vugt <daniel.van.vugt@canonical.com> | yes | 2018-03-16 | ||
| wayland-surface-Use-correct-default-viewport-for-surface-.patch | wayland/surface: Use correct default viewport for surface damage If no viewport is set, the neutral viewport is the surface size without viewport destination size applied - i.e. transform and scale applied to the buffer size. Change it accordingly, giving us the same values we'd return in `get_width` in this case. As result, this only changes cases where a viewport destination size but no viewport source rectangle is set. The change fixes exactly such cases, e.g. the Gstreamer Wayland sink. Can be tested with: `gst-play-1.0 --videosink=waylandsink`. (cherry picked from commit c1668116959664f04e509130e76a18d55429ca65) |
Robert Mader <robert.mader@collabora.com> | no | upstream, 3.38.7, commit:aeda2cbcd86e7f41e451c487f6d3ddadc3860c4a | 2021-12-18 | |
| wayland-surface-Do-not-uncoditionally-process-surface-dam.patch | wayland/surface: Do not uncoditionally process surface damage Most clients nowadays switched to buffer damage, most notably Mesa and Xwayland. Thus lets avoid the extra cost of allocating three `cairo_region_t`s and doing some calculations. (cherry picked from commit c498ae337f57a67c6e678d549cf9a8070c32f251) |
Robert Mader <robert.mader@collabora.com> | no | upstream, 3.38.7, commit:0b26ad635e703dc5cd1255933253c4dd40d611d5 | 2021-12-18 | |
| monitor-manager-Don-t-include-generated-code-in-header-fi.patch | monitor-manager: Don't include generated code in header file Meson doesn't seem to handle depending on generated headers, at least when those headers are pulled in indirectly via another header file. Luckily, we don't actually need to include the generated D-Bus boiler plate in meta-monitor-manager-private.h, since the MetaMonitorManager type no longer is based on the D-Bus service skeleton. So, by moving the inclusion of the generated D-Bus header file into meta-monitor-manager.c, we should hopefully get rid of the sporadic build issues. |
=?utf-8?q?Jonas_=C3=85dahl?= <jadahl@gmail.com> | yes | upstream | upstream, 40.1, commit:91117bb052ed0d69c8ea4159c1df15c814d90627 | 2021-04-12 |
| theme-use-gtk_render_icon_suface-to-paint-button-icon.patch | theme: use gtk_render_icon_suface to paint button icon This will properly take care of the icon transformations and of the shadow. Fixes #100 |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | invalid | upstream | 2018-03-30 | |
| theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch | theme: load icons as Gtk does with fallback and RTL support | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | invalid | 2018-03-30 | ||
| meson-add-back-default_driver-option.patch | meson: add back default_driver option In autotools it was possible to pass the --with-default-driver option to force the usage of a specific cogl driver at build time. Expose this functionality in meson as well |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | invalid | https://gitlab.gnome.org/GNOME/mutter/merge_requests/392 | 2019-01-16 |