imwayland: destroy objects only if it matches our manager object

Should fix one of the crash from #129.

Bug: https://gitlab.gnome.org/GNOME/gtk/issues/129
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894388
Forwarded: https://gitlab.gnome.org/GNOME/gtk/merge_requests/89
Applied-upstream: no

Gbp-Pq: Name 0016-imwayland-destroy-objects-only-if-it-matches-our-man.patch

m4macros: Fix underquoting in AC_PATH_TOOL

While these lines are being changed anyway, they might as well be
more correct.

Signed-off-by: Simon McVittie <smcv@debian.org>
Bug: https://gitlab.gnome.org/GNOME/gtk/issues/133
Applied-upstream: 3.22.30, commit:323d86b6e4bb19f252328a78e93fda03e1d9c0df

Gbp-Pq: Name 0015-m4macros-Fix-underquoting-in-AC_PATH_TOOL.patch

AM_PATH_GTK_3_0: Use AC_PATH_TOOL to find pkg-config

AM_PATH_GTK_3_0 uses AC_PATH_PROG for finding pkg-config. Unfortunately,
that will find the build architecture pkg-config which in turn will miss
the host architecture gtk+3.0. What must be used here is the host
architecture pkg-config and that is found with AC_PATH_TOOL.

Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894069
Reviewed-by: Simon McVittie <smcv@debian.org>
Bug: https://gitlab.gnome.org/GNOME/gtk/issues/133
Applied-upstream: 3.22.30, commit:3a7fbb3b30f6ed8f65f9f5862c2fd30035a1a1ed

Gbp-Pq: Name 0014-AM_PATH_GTK_3_0-Use-AC_PATH_TOOL-to-find-pkg-config.patch

wayland: Drop cairo surfaces when withdrawing

If a window is unmapped by the client while gdk is processing updates,
(for example Firefox un-mapping its window on Expose events), the
windowing backend resources might be lost (for example with Wayland)
which can cause a crash in end_paint().

Make sure we drop the cairo surfaces as well when hiding the surface,
that will avoid the crash in gdk_window_impl_wayland_end_paint() when
trying to attach the staging cairo surface to a released wl_surface,
these will be recreated when needed when the surface becomes visible
again and there is no need to keep such buffers around for a surface
which is not visible anyway.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=793062
Origin: upstream, 3.22.30, commit:3bd7b379c8d2c7e57ce22501420791c4bfcf24ca

Gbp-Pq: Name 0013-wayland-Drop-cairo-surfaces-when-withdrawing.patch

widget: Only print allocation warnings with --enable-debug

i.e. if G_ENABLE_CONSISTENCY_CHECKS is defined. This makes sense,
considering that this warning is about consistency of internal widget
state.

Origin: upstream, 3.22.30, commit:eb01ba8573bec47e02c8fc4eaf10e2f7cff522dd

Gbp-Pq: Name 0012-widget-Only-print-allocation-warnings-with-enable-de.patch

gtkstylecontext: guard against gtk_css_widget_node_get_widget() returning NULL in more places

When the widget gets finalized it clears the widgetnode and gtk_css_widget_node_get_widget
returns NULL. Guard against gtk_css_widget_node_get_widget() returning NULL like in other
places.

See https://gitlab.gnome.org/GNOME/pygobject/issues/28#note_82862

Origin: upstream, 3.22.30, commit:d65a4c2e0abeefb1e61e32a2da2c1e1ba9987817

Gbp-Pq: Name 0011-gtkstylecontext-guard-against-gtk_css_widget_node_ge.patch

imwayland: Avoid TOGGLE_INPUT_PANEL requests if there's no focus

Fixes two things: 1) As GTK+ can be coerced into using the wayland IM
module despite the compositor not implementing the interface, all paths
not checking for global state before sending requests are prone to
crashes, this one fell hit this pitfall.

And 2) ensures the tap gesture only triggers TOGGLE_INPUT_PANEL if the
widget IM is focused. This is a possibility on eg. WebKit pages, where
its IM is only focused as long as a form element in the page is focused.
Tapping elsewhere shouldn't toggle the OSK.

Origin: upstream, 3.22.30, commit:4f78abddfc8a815a7e02f5347d5326412190f66f
Bug: https://gitlab.gnome.org/GNOME/gtk/issues/114
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893696

Gbp-Pq: Name 0010-imwayland-Avoid-TOGGLE_INPUT_PANEL-requests-if-there.patch

gtkimmodule: make match_backend() query the wayland registry

Wnen _gtk_im_module_get_default_context_id calls
match_backend (context_id) and the default GdkDisplay
is wayland, match_backend() should return TRUE only if
gdk_wayland_display_query_registry (display, "gtk_text_input_manager")
returns TRUE.

Origin: upstream, 3.22.30, commit:6e2d14037cea356638a9bea7b611cbe23bc90b47
Bug: https://gitlab.gnome.org/GNOME/gtk/issues/114
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893696

Gbp-Pq: Name 0009-gtkimmodule-make-match_backend-query-the-wayland-reg.patch

gdk/x11: Check if we have access to GL before using GLX API

If the platform does not have access to libGL then any call to GL and
GLX API through libepoxy will fail with an assertion. Until such time
that libepoxy exposes API for us to use, we can simply dlopen libGL
ourselves and do a symbol check.

[smcv: fix typo]

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=775279
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366
Applied-upstream: no, GTK+ 4 added a dependency on newer libepoxy instead

Gbp-Pq: Name gdk-x11-Check-if-we-have-access-to-GL-before-using-G.patch

Mark known failing tests as non-fatal

Forwarded: no

Gbp-Pq: Name reftest-known-fail.patch

disable a11y test accessibility-dump

Temporarily disable this test until someone figures out how
to make it run with GTK_CSD=1 properly so it gives output
matching the expected test data in all cases, not just
for installed-tests.

Forwarded: no

Gbp-Pq: Name no-accessibility-dump.patch

Don't list images from unknown directories in icon cache

After GTK+ 2.12.0, gtk-update-icon-cache fails if there is a PNG file
placed directly in /usr/share/icons/hicolor (not in a correct
subdirectory like 48x48/apps).

TODO: This is believed to have been fixed differently upstream, so maybe
this change is no longer necessary:
"I believe a slightly different fix that I did some time ago fixes this
too." --Matthias Clasen, 2008-02-16 04:43:10 UTC

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=451634
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444285
Forwarded: yes
Applied-upstream: no

Gbp-Pq: Name 060_ignore-random-icons.patch

Disable VIQR IM for vi locale

[TODO: why? The Debian changelog just says "imported from Ubuntu"]

Forwarded: no

Gbp-Pq: Name 022_disable-viqr-im-for-vi-locale.patch

Consistently treat gdkenumtypes.[hc] as source files

Always generate gdk/gdkenumtypes.c in the source tree, and fix path in the
introspection sources. With this, gdkenumtypes.c is correctly included with
separate build trees, too. This fixes missing GTypes in the .gir when using a
separate build tree.

Also remove the gdk/stamp-gdkenumtypes.h target. It was forcing the
regeneration of gdk/gdkenumtypes.h even if it was already present and current
in the source tree.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=647729
Bug-Ubuntu: https://launchpad.net/bugs/769256
Forwarded: yes

Gbp-Pq: Name 018_gdkenumtypes.c_location.patch

Do not allow devices in an offscreen hierarchy to take grabs.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=658563
Bug-Ubuntu: https://launchpad.net/bugs/804009
Forwarded: yes

Gbp-Pq: Name 017_no_offscreen_device_grabbing.patch

Don't let offscreen widget do grabbing

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=607668
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=658563
Bug-Ubuntu: https://bugs.launchpad.net/bugs/512427
Forwarded: yes

Gbp-Pq: Name 016_no_offscreen_widgets_grabbing.patch

gtk+3.0 (3.22.29-3) unstable; urgency=medium

  * Team upload
  * Allow stderr in autopkgtests. They produce harmless diagnostics.
  * d/p/0013-wayland-Drop-cairo-surfaces-when-withdrawing.patch:
    Add patch from upstream fixing a Wayland client crash if it unmaps
    a window while gdk is processing updates
  * d/p/0014-AM_PATH_GTK_3_0-Use-AC_PATH_TOOL-to-find-pkg-config.patch,
    d/p/0015-m4macros-Fix-underquoting-in-AC_PATH_TOOL.patch:
    Use AC_PATH_TOOL to find pkg-config in the deprecated AM_PATH_GTK_3_0
    macro (Closes: #894069)
  * d/p/0016-imwayland-destroy-objects-only-if-it-matches-our-man.patch:
    Add patch proposed upstream to fix crashes on screen blank in some
    dual-monitor configurations (Closes: #894388)

[dgit import unpatched gtk+3.0 3.22.29-3]

Import gtk+3.0_3.22.29-3.debian.tar.xz

[dgit import tarball gtk+3.0 3.22.29-3 gtk+3.0_3.22.29-3.debian.tar.xz]

Import gtk+3.0_3.22.29.orig.tar.xz

[dgit import orig gtk+3.0_3.22.29.orig.tar.xz]