gtk+3-3.24.36

[Bruce Dubbs]

New point version.

[martyj19]

Sloppy release engineering. Sadly, take the release media to another clean system and try to install it has been a good idea since at least 1975 and is news to this project.

https://gitlab.gnome.org/GNOME/gtk/-/issues/5355

[martyj19]

Now 3.24.36. The fault that caused the hold is resolved.

[pierre]

Overview of Changes in GTK+ 3.24.35, 11-22-2022

• GtkFontChooserWidget:
  • Fix a critical

• GtkAccelLabel:
  • Differentiate keypad keysyms in accelerators

• Input:
  • Recognize stylus devices as pens
  • Fix problems with motion compression

• Windows:
  • Build system improvements

• Wayland:
  • Fix problems with unreliable DND
  • Use GLES if required
  • Add support for titlebar gestures
  • Refactor handling of IM client updates
  • Fix cursor hotspots with scaled surfaces
  • Use the xdg-activation protocol
  • Load cursors on demand
  • Fix cursor size on hi-dpi displays

• MacOS:
  • Use a CVDisplayLink based frame clock

• Translation updates:

Overview of Changes in GTK+ 3.24.36, 12-22-2022

This release is the first GTK 3 release to exclusively use the meson build system.

• GtkLabel:
  • Tweak selection behavior

• GtkEmojiChooser:
  • Properly handle empty recent section

• GtkFileChooser:
  • Make ~ key work regardless of dead keys

• build:
  • Improve handling of flaky tests
  • Drop the autotools build

• Wayland:
  • Fix problems with X<>Wayland DND
  • Revert cursor changes from 3.24.35
  • Fix handling of surrounding text in input

• Windows:
  • Improve handling of line ends in clipboard

• MacOS:
  • Use NSTrackingArea

• Translation updates:

[pierre]

As seen above, the build system is now meson only... I have some problems with two tests that are not finished after 30 s, so that meson times them out. But if I run the tests with meson test -t -1 --print-errorlogs --no-rebuild (a negative value for timeout disables timeout), I then get (only one of the tests shown):

 66/196 gtk+:gtk / defaultvalue                                          FAIL           34.44s   killed by signal 5 SIGTRAP

It's weird upstream don't get a failure when running their CI, so I'm inclined to think there may be a problem with the way I build. BTW, I use:

meson setup --prefix=/usr           \
            -Dman=true              \
            -Dbroadway_backend=true \
            .. &&
ninja

then ninja test or the command above. Not sure whether I need --buildtype=release.

Well, just tried --buildtype=release, no change.

[pierre]

Fixed at 7036577121