← Back to team overview

debcrafters-packages team mailing list archive

  1. debcrafters-packages team
  2. Mailing list archive
  3. Message #00012

[Bug 2109978] Re: [SRU] Update gtk4 to 4.14.5 for Noble

  Thread Previous • Date Previous • • Thread Next 
** Description changed:

  [ Impact ]
  
  4.14.5 is a new bugfix release from upstream:
- https://gitlab.gnome.org/GNOME/gtk/-/blob/4.18.5/NEWS?ref_type=tags
+ https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/NEWS?ref_type=tags
  
- * Bugs fixed:
-   - #5844 `gdk_surface_get_device_position: assertion 'GDK_IS_SURFACE (surface)'
-     failed` on popover close (Alessandro Astone)
-   - #7451 Cairo device scale changes lead to significant performance regression
-     in cairo blur (Sebastian Keller) (bug 2107245)
-   - #7479 gtkmm programs fail to start on Windows with AccessKit support enabled
-     (Matthias Clasen)
-   - #7482 Epiphany Crash in GTK file chooser when last used directory has
-     insufficient filesystem permissions: "GFileInfo created without
-     standard::type" (Philip Withnall)
-   - #7495 Failed to link with the mold linker (Matthias Clasen)
-   - #7513 Broken boxed-list ListBox (Sergey Bugaev)
-   - #7520 XCompose preventing GTK4 applications from launching (again) (Matthias
-     Clasen)
-   - #7522 critical when selecting label with use-underline but mnemonic with
-     screenreader enabled (Markus Göllnitz)
+ * Some notable bugs that motivated this SRU:
+   - upstream MR #7535 ci: avoid another date-dependent failure (Jeremy Bícha), allows building on 31st day of the month.
+   - salsa #1077287 / LP #2098698 debian: Depend on libgles2 (Simon McVittie)
  
  [ Test Plan ]
  
- Test Case 0
- -----------
+ Test Case 0 - ci
+ ----------------
  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
- -----------
+ Test Case 1 - gtk4-demo on containers
+ --------------------------------------
+ Setup an Ubuntu 24.04 container (Ubuntu on WSL instance also works).
+ Make sure it doesn't contain the libgles2 package already installed.
+ Update apt cache and install gtk-4-examples and try running gtk4-demo.
+ With previous versions of GTK4 it fails to launch due libgles2.so not found. With this version debian/control explicitly defines the dependency so apt installs libgles2.
+ 
+ 
+ Test Case 2 - build on day 31st
+ -------------------------------
+ Adjust your system date to Jan 31st of the current year and try to build the binary packages. Package tests should fail with previous versions of this source package.
+ Alternatively, you can test the specific part of the sources causing trouble: Set your system calendar to the 31st day of the month (for instance July 31)
+ 
+ cd testsuite/gtk
+ gcc -o notify notify.c $(pkgconf --cflags --libs gtk4 gtk4-unix-print)
+ ./notify
+ The test should complete successfully like it does if it is not the 31st day of the month.
+ 
+ 
+ Test Case 3 - portal-test snap
+ -------------------------------
  snap install portal-test --edge
  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.
+ 
+ Test Case 4 - GNOME apps
+ ------------------------
+ Install and test 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 using GTK4. 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.
  
  [ Other info ]
  
  gtk4 is included in the GNOME micro release exception.
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2109978

Title:
  [SRU] Update gtk4 to 4.14.5 for Noble

Status in gtk4 package in Ubuntu:
  New

Bug description:
  [ Impact ]

  4.14.5 is a new bugfix release from upstream:
  https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/NEWS?ref_type=tags

  * Some notable bugs that motivated this SRU:
    - upstream MR #7535 ci: avoid another date-dependent failure (Jeremy Bícha), allows building on 31st day of the month.
    - salsa #1077287 / LP #2098698 debian: Depend on libgles2 (Simon McVittie)

  [ Test Plan ]

  Test Case 0 - ci
  ----------------
  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 - gtk4-demo on containers
  --------------------------------------
  Setup an Ubuntu 24.04 container (Ubuntu on WSL instance also works).
  Make sure it doesn't contain the libgles2 package already installed.
  Update apt cache and install gtk-4-examples and try running gtk4-demo.
  With previous versions of GTK4 it fails to launch due libgles2.so not found. With this version debian/control explicitly defines the dependency so apt installs libgles2.

  
  Test Case 2 - build on day 31st
  -------------------------------
  Adjust your system date to Jan 31st of the current year and try to build the binary packages. Package tests should fail with previous versions of this source package.
  Alternatively, you can test the specific part of the sources causing trouble: Set your system calendar to the 31st day of the month (for instance July 31)

  cd testsuite/gtk
  gcc -o notify notify.c $(pkgconf --cflags --libs gtk4 gtk4-unix-print)
  ./notify
  The test should complete successfully like it does if it is not the 31st day of the month.

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

  
  Test Case 4 - GNOME apps
  ------------------------
  Install and test 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 using GTK4. 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.

  [ Other info ]

  gtk4 is included in the GNOME micro release exception.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2109978/+subscriptions
  Thread Previous • Date Previous • • Thread Next