debcrafters-packages team mailing list archive

[Sergio Costas <2122598@xxxxxxxxxxxxxxxxxx>]

Modified the patch to always force Cairo in GTK4 when compiled for
s390x.

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

Title:
  Gtk4 deb package doesn't build in s390x architecture

Status in gtk4 package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  In Progress
Status in gtk4 source package in Plucky:
  Invalid
Status in gtk4 source package in Questing:
  Invalid

Bug description:
  [ Impact ]

  There are a number of gtk4 tests (build-time, and again at autopkgtest
  time) that are failing on s390x *only* when run in the combination of
  an updated mesa package (25.0.7-0ubuntu0.24.04.1) in Noble.

  The problem seems to be in the GtkWidgetPaintable widget, which isn't
  triggering the "invalidate-contents" signal. This signal should be
  triggered every time the canvas has been repainted, and it is used in
  the tests to know when it is safe to capture the rendered picture and
  compare it with the expected results.

  Setting `GSK_RENDERER=cairo` uses pure software rendering, and makes
  this work again.

  s390x is not a desktop platform, there are no desktop images for it,
  and gtk4 is not seeded in that architecture. While it would be best to
  fully understand what is making these tests fail, it's best to use
  this workaround for now in that architecture only, so that users in
  other architectures can benefit from the mesa and gtk4 updates.

  This bug affects not only GTK4 build, but also Gnome Control Center
  build.

  [ Test Plan ]
  The failure manifests itself in the build-time tests, which are again repeated at autopkgtest time. Therefore, the test plan consists of:
  - no build failure in any platform, and specifically s390x
  - no autopkgtest failure in any platform, and specifically s390x

  Specifically, we also don't want any change in the number of tests run
  in non-s390x architectures.

  amd64 and arm64:
  x11:
  Ok: 655
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 13
  Timeout: 0
  wayland:
  Ok: 657
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 11
  Timeout: 0

  armhf:
  x11:
  Ok: 578
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 2
  Timeout: 0
  wayland:
  Ok: 569
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 11
  Timeout: 0

  i386:
  x11:
  Ok: 576
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 2
  Timeout: 0
  wayland:
  Ok: 567
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 11
  Timeout: 0

  ppc64el:
  x11:
  Ok: 655
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 13
  Timeout: 0
  wayland:
  Ok: 657
  Expected Fail: 0
  Fail: 0
  Unexpected Pass: 0
  Skipped: 11
  Timeout: 0

  riscv64:
  Build time tests are not run:
  dh: command-omitted: The call to "debian/rules override_dh_auto_test" was omitted due to "DEB_BUILD_OPTIONS=nocheck"

  s390x should have no tests with a timeout result in proposed.

  [ Where problems could occur ]

  The available patch forces Cairo as the renderer and keeps the tests,
  so, in case that there are problems with any application, we can
  recommend to set `GSK_RENDERER=cairo` in the system. That should make
  everything work.

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