Update gtk4 to 4.16.3

[Jeremy Bícha]

There is a new point release in the stable GTK 4.16 series.

https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS

Test Case 0
-----------
gtk4 has an extensive build test suite, and failures will fail the build.
gtk4 also has thorough autopkgtests.
Ensure that the build succeeds and that the autopgktests pass.

Test Case 1
-----------
Make sure that opening and saving files from the Firefox and Chromium snaps still work

Test Case 2
-----------
snap install portal-test
snap run portal-test
Verify that the app seems to still work ok

Test Case 3
-----------
Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected.

What Could Go Wrong
-------------------
Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop.

Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU.

gtk4 is included in the GNOME micro release exception.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

[Chris Halse Rogers (raof)]

Hello Jeremy, or anyone else affected,

Accepted gtk4 into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk4/4.16.3+ds-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gtk4 - 4.16.5+ds-1

---------------
gtk4 (4.16.5+ds-1) experimental; urgency=medium

  [ Simon McVittie ]
  * New upstream release
  * d/p/printing-If-we-cannot-contact-Avahi-debug-log-the-error-m.patch,
    d/p/printing-Treat-any-G_DBUS_ERROR-contacting-Avahi-as-non-p.patch:
    Drop patches that were applied upstream
  * d/tests/run-with-display: Send xvfb-run output to stderr
    (helps: #1082659, #1084230)

  [ Jeremy Bícha ]
  * Quote cpdb dependency to fix Ubuntu build

 -- Simon McVittie <email address hidden> Tue, 05 Nov 2024 12:25:51 +0000