[SRU] GLArea transparency broken

[Robert Ancell]

[Impact]

In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42).

[Test Case]

Run gdkgears:
$ apt source gtk+3.0
$ cd src/gtk+3.0-3.24.41
$ meson _build
$ ninja -C _build
$ ./_build/tests/gdkgears
Click "Alpha" checkbox.

Expected results:
Gears are shown with Gtk window background behind them.

Observed results:
Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames).

[Regression potential]

Issues can be expected in GTK3 widgets with a transparent background.

[Nathan Teodosio (nteodosio)]

I confirmed the fix in 24.04 and created https://salsa.debian.org/gnome-team/gtk3/-/merge_requests/24 for it.

[Sebastien Bacher (seb128)]

I've reviewed/merged/uploaded the fix now

[Timo Aaltonen (tjaalton)]

Hello Robert, or anyone else affected,

Accepted gtk+3.0 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.41-4ubuntu1.2 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted gtk+3.0 (3.24.41-4ubuntu1.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

apport/unknown (armhf)
bookletimposer/unknown (armhf)
dogtail/0.9.11-12 (armhf)
gnome-mastermind/0.4.0-4build2 (armhf)
gspell/1.12.2-1build4 (armhf)
gtksourceview4/unknown (armhf)
lablgtk3/3.1.4-1build3 (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.2 (armhf)
netmate/unknown (armhf)
openjdk-21/21.0.4+7-1ubuntu2~24.04 (arm64)
openssh/1:9.6p1-3ubuntu13.5 (ppc64el)
slic3r-prusa/2.7.2+dfsg-1build2 (arm64)
surf/unknown (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#gtk+3.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Robert Ancell (robert-ancell)]

Attempted to verify this today but 3.24.41-4ubuntu1.2 is not downloading from proposed - is it held due to the autopkgtest results above?

[Sebastien Bacher (seb128)]

The autopkgtests have no impact on publication. When you say 'not downloading', do you mean that apt doesn't see the update? Are you maybe using an outdated mirror?

$ rmadison libgtk-3-0t64 -s noble-proposed
 libgtk-3-0t64 | 3.24.41-4ubuntu1.2 | noble-proposed | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

you can download the deb artifacts from https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.41-4ubuntu1.2/+build/28920277 otherwise

[Robert Ancell (robert-ancell)]

Couldn't work out why they aren't updating automatically but manually installing the .debs shows the issue fixed, thanks!

[Andreas Hasenack (ahasenack)]

I retried many autopkgtests just now.

[Andreas Hasenack (ahasenack)]

> Couldn't work out why they aren't updating automatically but manually installing the .debs shows the
> issue fixed, thanks!

Thanks Robert for your verification, but could you please expand on what verification steps you actually performed, and with which package versions? The instructions request:

> 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.

The test plan has very detailed steps that should have been followed.

Regarding your issue with having apt recognize the packages from proposed, did you add the "-t noble-proposed" command-line parameter?

In the meantime, I'm flipping the tags back to verification-needed.

[Robert Ancell (robert-ancell)]

Reverifying using the new method:

Installed `sudo apt install libgtk-3-0t64 -t noble-proposed`.
Got source using `apt source gtk+3.0 -t noble-proposed`

Confirmed GTK 3 version installed is 3.24.41-4ubuntu1.2.

Ran test case listed in bug description, confirmed rendering correctly (see attached screenshot).

Also ran Flutter application that uses this feature and confirmed that works (where original issue was noticed).

[Launchpad Janitor (janitor)]

This bug was fixed in the package gtk+3.0 - 3.24.41-4ubuntu1.2

---------------
gtk+3.0 (3.24.41-4ubuntu1.2) noble; urgency=medium

  * d/p/glarea-transparency: Fix GLArea transparency regression. (LP: #2077290)

 -- Nathan Pratta Teodosio <email address hidden> Wed, 28 Aug 2024 10:09:51 +0200

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.