| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Update-Abkhazian-translation.patch | Update Abkhazian translation | Nart Tlisha <daniel.abzakh@gmail.com> | no | upstream, 4.8.4, commit:1e27563425094d40bbf14a2c0c38ebb134753baf | 2023-01-05 | |
| gtkcolumnviewcolumn-Only-create-cells-when-the-column-is-.patch | gtkcolumnviewcolumn: Only create cells when the column is visible Merge branch 'wip/corey/list-item-visible' into 'main' See merge request GNOME/gtk!5374 (cherry picked from commit 188f9269b7e25847d4d50ba12c004f5da81aa352) |
Benjamin Otte <otte.benjamin@googlemail.com> | no | upstream, 4.8.4, commit:2aaefd9ff67446bcd0fdee90fe0ed3ac8c02fb12 | 2022-12-29 | |
| Update-Turkish-translation.patch | Update Turkish translation | =?utf-8?q?Sabri_=C3=9Cnal?= <libreajans@gmail.com> | no | upstream, 4.8.4, commit:4a38d5d1d53326bf4444146c665e92800b827243 | 2023-01-11 | |
| Update-Turkish-translation-1.patch | Update Turkish translation | =?utf-8?q?Emin_Tufan_=C3=87etin?= <etcetin@gmail.com> | no | upstream, 4.8.4, commit:83284e6a9db63f84596a5c08c7d24b055df86b95 | 2023-01-11 | |
| gdk-surface-Handle-clicks-outside-client-surfaces.patch | gdk/surface: Handle clicks outside client surfaces The owner_events=TRUE grab makes GDK on X11 see events happening outside every client window as received on the grab window. Additionally check that the pointer is inside the grab window (i.e. it received GDK_CROSSING_NORMAL crossing events for the core pointer) in order to handle clicks happening outside client windows. These new paths are expected to be a no-op on Wayland, and to also work for touchscreen input on X11, due to emulated pointer events. |
Carlos Garnacho <carlosg@gnome.org> | yes | upstream | upstream, 4.8.4, commit:826030dcc2e79dcd76d21c118c6a0a3f0994c284 | 2022-12-23 |
| fontchooser-Drop-a-few-errant-translations.patch | fontchooser: Drop a few errant translations No point in translating these properties, they are not strings. |
Matthias Clasen <mclasen@redhat.com> | yes | upstream | upstream, 4.8.4, commit:92ebf8ab13ab7e24cb2d9971cafd52bc579ab3c3 | 2022-10-18 |
| gtkcssanimatedstyle-Fix-return-of-new_advance.patch | gtkcssanimatedstyle: Fix return of new_advance() This was causing animation and transition to stop randomly and reset their state to initial state. This issue has existed since commit 7b68bdb8316fc1bb96c4a5ad16c1885506131d22. |
Matteo Percivaldi <m.percivaldi@fastassembler.com> | yes | upstream | upstream, 4.8.4, commit:1ff3a26c9644fbcbd91107280ff1ef839d4ea2f2 | 2023-01-13 |
| Update-Turkish-translation-2.patch | Update Turkish translation | =?utf-8?q?Sabri_=C3=9Cnal?= <libreajans@gmail.com> | no | upstream, 4.8.4, commit:1ef03e6eb8f27d25b97df1b7bc766df402ad75a8 | 2023-01-15 | |
| gdk-x11-Reset-all-scroll-valuators-on-enter.patch | gdk/x11: Reset all scroll valuators on enter We no longer need to make much distinction between multiple logical devices, plus it breaks esp. with the Xwayland input device distribution. Just iterate across all devices and reset their scroll valuators. (cherry picked from commit 824e983372d939693f7eba5c394e647a9035a0f8) |
Carlos Garnacho <carlosg@gnome.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5479 | 2023-02-04 |
| placessidebar-Make-all-rows-ellipsize.patch | placessidebar: Make all rows ellipsize Otherwise, we end up with a single long row pushing the content of all the other rows off to the left, which is much worse than ellipsizing. |
Matthias Clasen <mclasen@redhat.com> | yes | debian upstream | 2023-02-03 | |
| testsuite-Use-separate-setups-for-unstable-tests-instead-.patch | testsuite: Use separate setups for unstable tests instead of should_fail There are two possible interpretations of "expected failure": either the test *must* fail (exactly the inverse of an ordinary test, with success becoming failure and failure becoming success), or the test *may* fail (with success intended, but failure possible in some environments). Autotools had the second interpretation, which seems more useful in practice, but Meson has the first. Instead of using should_fail, we can put the tests in one of two new according to the test environment or chance, while "failing" is for tests that ought to succeed but currently never do as a result of a bug or missing functionality. With a sufficiently new version of Meson, the flaky and failing tests are not run by default, but can be requested by running a setup that does not exclude them, with a command like: meson test --setup=x11_unstable --suite=flaky --suite=failing As a bonus, now that we're setting up setups and their excluded suites programmatically, the gsk-compare-broadway tests are also excluded by default when running the test setup for a non-broadway backend. When running the tests in CI, --suite=gtk overrides the default exclude_suites, so we have to specify --no-suite=flaky and --no-suite=failing explicitly. This arrangement is inspired by GNOME/glib!2987, which was contributed by Marco Trevisan. |
Simon McVittie <smcv@debian.org> | no | 2022-11-23 | ||
| testsuite-Don-t-create-.test-files-for-flaky-or-failing-t.patch | testsuite: Don't create .test files for flaky or failing tests These tests can be run manually, but are not suitable for use as an acceptance test, so let's not make frameworks like Debian's autopkgtest run these when they run ginsttest-runner in the most obvious way. |
Simon McVittie <smcv@debian.org> | no | 2022-11-23 | ||
| node-editor-Save-test-data-relative-to-current-working-di.patch | node-editor: Save test data relative to current working directory This avoids hard-coding the GTK source directory into the binary, which would make the binary non-reproducible across different source paths, particularly in a distro build environment where the source directory used by autobuilders will often not exist on end-user systems. The node editor can still be used to create new test-cases by running it with the GTK source directory as its current working directory. |
Simon McVittie <smcv@debian.org> | yes | upstream | 2022-12-06 | |
| 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 | 2021-02-13 | ||
| debian/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 | ||
| debian/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 | |
| debian/Disable-clipboard-test.patch | Disable clipboard test This regularly times out on buildds, but I can't reproduce the hang locally. |
Simon McVittie <smcv@debian.org> | no | upstream | 2021-09-03 |