debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #09537
[Bug 2122598] Re: Gtk4 deb package doesn't build in s390x architecture
Hello Sergio, or anyone else affected,
Accepted gtk4 into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk4/4.14.5+ds-0ubuntu0.6 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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.
** Tags added: verification-needed verification-needed-noble
--
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:
Fix Committed
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 the GTK4 package, but also any GTK4 app with
build tests or autopkgtests, such as Gnome Control Center:
https://launchpad.net/ubuntu/+source/gnome-control-
center/1:46.7-0ubuntu0.24.04.3
[ 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 in s390x, affecting all GTK4 applications. The renderer has limited capabilities vs the other OpenGL or Vulkan renderers, which may affect the look of some GTK4 applications.
However, s390x is not a primary desktop architecture and the alternative would be non-working applications since Mesa is misbehaving in s390x.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2122598/+subscriptions
References