Debian Patches
Status for gtk4/4.21.6+ds-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/reftest_compare_surfaces-Report-how-much-the-images-diffe.patch | reftest_compare_surfaces: Report how much the images differ In unattended/non-interactive/autobuilder environments where the images are not trivially accessible, this provides a way to distinguish between totally different rendering and more subtle issues. |
Simon McVittie <smcv@debian.org> | yes | 2024-08-31 | ||
| insttests/Revert-build-Drop-the-install-tests-option.patch | Revert "build: Drop the install-tests option" Debian and Ubuntu uses these installed tests as part of their autopkgtest system This reverts commit 3121f88265ac61733e257f5335473d6f139f158c. |
Jeremy Bicha <jeremy.bicha@canonical.com> | no | 2023-01-12 | ||
| insttests/Revert-testsuite-Remove-leftover-test.in-files.patch | Revert "testsuite: Remove leftover test.in files" This reverts commit b598f21506c31d3913c9705a00eb1e8270e9a810. |
Jeremy Bícha <jeremy.bicha@canonical.com> | no | 2024-12-06 | ||
| workarounds/reftests-Allow-minor-differences-to-be-tolerated.patch | reftests: Allow minor differences to be tolerated Based on an earlier patch by Michael Biebl, as used in Debian's GTK 3 packaging, with additional inspiration from librsvg's reftests. Each .ui or .node reftest can have an accompanying .keyfile file like this: [reftest] tolerated-diff-level=20 tolerated-diff-pixels=1000 If the image differs, but the number of pixels that differ is no more than tolerated-diff-pixels and the differences are no more than tolerated-diff-level, then we treat it as a success with warnings, save the .diff.png for analysis, and use g_test_incomplete() to record the test-case as "TODO". |
Simon McVittie <smcv@debian.org> | yes | 2021-02-13 | ||
| workarounds/Disable-inscription-markup.ui-reftest.patch | Disable inscription-markup.ui reftest It's rendered 1px to the left of where it should be, which is not a serious problem for practical use of GTK, but is a test failure. |
Simon McVittie <smcv@debian.org> | not-needed | upstream | 2022-08-12 | |
| workarounds/tests-Mark-gltexture-as-expected-to-fail-on-big-endian-ma.patch | tests: Mark gltexture as expected to fail on big-endian machines | Simon McVittie <smcv@debian.org> | not-needed | 2023-08-22 | ||
| workarounds/tests-Allow-longer-for-a-dialog-to-open.patch | tests: Allow longer for a dialog to open This hopefully makes the test pass more reliably, especially on riscv64. |
Simon McVittie <smcv@debian.org> | invalid | debian upstream | 2023-08-22 | |
| workarounds/nodeparser-Adjust-test-for-pango-1.52.0.patch | nodeparser: Adjust test for pango 1.52.0 Adjust test result for changed output resulting from https://gitlab.gnome.org/GNOME/pango/-/commit/d489fc8c4 |
Jeremy Bícha <jeremy.bicha@canonical.com> | yes | 2024-03-09 | ||
| workarounds/testsuite-skip-color-mix.patch | testsuite: skip color-mix https://gitlab.gnome.org/GNOME/gtk/-/issues/6907 |
Jeremy Bícha <jeremy.bicha@canonical.com> | no | 2024-08-06 | ||
| workarounds/scaling-test-Skip-floating-point-pixel-formats-with-Cairo.patch | scaling test: Skip floating-point pixel formats with Cairo renderer If the four chosen pixel values happen to have alpha values that average to 16/17, GTK will quantize that into 8bpp integer space as 16/17*255 = 240, but Cairo/Pixman does its quantization differently and gets 16/17*256 = 241. |
Simon McVittie <smcv@debian.org> | yes | upstream | 2024-09-03 | |
| workarounds/nodeparser-Mark-failing-tests-on-s390x.patch | nodeparser: Mark failing tests on s390x | Alessandro Astone <alessandro.astone@canonical.com> | not-needed | upstream | 2025-08-18 | |
| workarounds/testsuite-Skip-vulkan-tests-that-break-lavapipe.patch | testsuite: Skip vulkan tests that break lavapipe | Alessandro Astone <alessandro.astone@canonical.com> | not-needed | 2026-02-10 | ||
| x11-scale/gdk-x11-check-surface-scale-on-input-region-opaque-region.patch | gdk/x11: check surface scale on input region, opaque region/rect Since in x11 backend the input region, opaque region and opaque rect are related to scale, it is necessary to track whether the scale is different so these regions can be updated without changing the logical size. |
Yao Wei <medicalwei@gmail.com> | yes | upstream | 2025-12-19 | |
| x11-scale/gdk-x11-update-correct-shadow-size-according-to-window-si.patch | gdk/x11: update correct shadow size according to window size change Because update_shadow_size is not updated since the logical size of shadow is not changed, the shadow is glitched out. This makes sure that the shadow size is recalculated when the scale is changed. |
"Yao Wei (魏銘廷)" <yao.wei@canonical.com> | yes | upstream | 2025-10-03 | |
| x11-scale/gdk-x11-update-cursor-size-on-the-extent-after-scale-chan.patch | gdk/x11: update cursor size on the extent after scale change This will update the cursor size when the scale is changed. When gnome-shell under Xorg is started in 2x, scaling the UI to 1x the cursor size is correctly scaled to 1x, but it does not work the other way round. |
"Yao Wei (魏銘廷)" <yao.wei@canonical.com> | yes | upstream | 2025-10-03 | |
| testsuite-Skip-gestures-if-running-with-no-seat.patch | testsuite: Skip gestures if running with no seat Like 8912a6eb757c39a6801358331fa81f8f52ebad8a |
Alessandro Astone <alessandro.astone@canonical.com> | yes | 2026-03-05 |
All known versions for source package 'gtk4'
- 4.21.6+ds-1 (sid)
- 4.21.5+ds-5 (forky)
- 4.18.6+ds-2 (trixie)
- 4.8.3+ds-2+deb12u1 (bookworm)
