Include gtk3 changes needed for mutter 42.1

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.33-1ubuntu2 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

All autopkgtests for the newly accepted gtk+3.0 (3.24.33-1ubuntu2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gjs/1.72.0-3~ubuntu22.04.1 (ppc64el)
ubuntu-release-upgrader/1:22.04.10 (ppc64el, s390x, arm64)
apport/2.20.11-0ubuntu82 (amd64)

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/jammy/update_excuses.html#gtk+3.0

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

Thank you!

After installing the gtk3 3.24.33-1ubuntu2 proposed updates, I confirm that scrolling down in long documents in gedit works with both the jammy mutter 42.0-3ubuntu2 and the jammy-proposed version 42.1-0ubuntu1.

This bug was fixed in the package gtk+3.0 - 3.24.33-2ubuntu1

---------------
gtk+3.0 (3.24.33-2ubuntu1) kinetic; urgency=medium

  * Resynchronize with Debian, remaining changes
    + Install a settings.ini file to set our themes
    + Update debian/libgtk-3-0.symbols
    + debian/control.in and debian/tests/control (installed-tests):
      - Build-depend on adwaita-icon-theme-full for icon name check test
    + debian/control.in: Build-Depend on dh-sequence-translations
    + Ubuntu-specific patches:
      - 073_treeview_almost_fixed.patch
      - bzg_gtkcellrenderer_grabbing_modifier.patch
      - ubuntu_gtk_custom_menu_items.patch
      - print-dialog-show-options-of-remote-dnssd-printers.patch
      - uimanager-guard-against-nested-node-updates.patch
      - x-canonical-accel.patch
      - message-dialog-restore-traditional-look-on-unity.patch
      - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
      - restore_filechooser_typeaheadfind.patch
      - 0001-calendar-always-emit-day-selected-once.patch
      - 0001-gtkwindow-set-transparent-background-color.patch
      - unity-border-radius.patch
      - unity-headerbar-maximized-mode.patch

gtk+3.0 (3.24.33-2) unstable; urgency=medium

  * Cherry-pick gtk-3-24 commits needed for mutter 42.1 (LP: #1972721)

 -- Jeremy Bicha <email address hidden> Mon, 09 May 2022 16:12:01 -0400

This bug was fixed in the package gtk+3.0 - 3.24.33-1ubuntu2

---------------
gtk+3.0 (3.24.33-1ubuntu2) jammy; urgency=medium

  * Cherry-pick gtk-3-24 commits needed for mutter 42.1 (LP: #1972721)

 -- Jeremy Bicha <email address hidden> Mon, 09 May 2022 16:15:04 -0400

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.