← Back to team overview

debcrafters-packages team mailing list archive

[Bug 2119291] Re: mesa 25.0.7 SRU breaks gtk4 on s390x

 

The problem seems to be that GtkWidgetPaintable isn't triggering the
"invalidate-contents" signal.

The test code related with the bug is `gtk-reftest.c'. In the
`test_ui_file()`
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/testsuite/reftests/gtk-
reftest.c?ref_type=tags#L349 function it calls
`reftest_snapshot_ui_file()`
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/testsuite/reftests/reftest-
snapshot.c?ref_type=tags#L296 to generate an snapshot of the GTK
interface defined by an `.ui` file (which later would be compared with
the interface generated by a file with the same name, but ended in
`.ref.ui`). That function creates the UI using GtkBuilder(), and then it
calls `snapshot_widget()`
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/testsuite/reftests/reftest-
snapshot.c?ref_type=tags#L270 .

This is the function that creates the snapshot itself. To do so, it
creates a GtkWidgetPaintable from the passed window, connects to the
"invalidate-contents" signal, and enters a GMainLoop to wait for it.
When it arrives, it calls `draw_paintable()`
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.14.5/testsuite/reftests/reftest-
snapshot.c?ref_type=tags#L223 which creates the picture and launches an
idle timeout to quit the GMainLoop.

Unfortunately, in some of the tests, the signal is never triggered by
the GtkWidgetPaintable, so `draw_paintable()` is never called and the
test never exits the GMainLoop.

-- 
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/2119291

Title:
  mesa 25.0.7 SRU breaks gtk4 on s390x

Status in gtk4 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  First seen in the autopkgtest:

  https://autopkgtest.ubuntu.com/packages/g/gtk4/noble/s390x

  mesa 25.0.7-0ubuntu0.24.04.1 regresses the autopkgtest of gtk4
  4.14.5+ds-0ubuntu0.1 on s390x.

  42515s build-x11            PASS (superficial)
  42515s build-wayland        FAIL timed out
  42515s python3-gi-x11       PASS (superficial)
  42515s python3-gi-wayland   FAIL timed out
  42515s installed-tests-x11  PASS
  42515s installed-tests-wayland FAIL non-zero exit status 2
  42515s installed-tests-flaky-x11 FLAKY non-zero exit status 2
  42515s installed-tests-flaky-wayland FLAKY non-zero exit status 2

  The build-wayland and python3-gi-wayland autopkgtests do not terminate
  and eventually hit the time out.

  We have tried running the tests on a bigger instance (added to
  'big_packages') and have tried triggering the tests with 'all-
  proposed=1'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2119291/+subscriptions



References