gtk-shell: Work around non-working startup notifications
authorFlorian Müllner <fmuellner@gnome.org>
Thu, 20 Oct 2016 16:00:04 +0000 (18:00 +0200)
committerSimon McVittie <smcv@debian.org>
Wed, 6 Feb 2019 10:02:14 +0000 (10:02 +0000)
commitf380d4b0cdb24eedaaf7fb06e3b6ba3ecce8b0ab
tree1ca486d6363b1de93619bbc3bbc574229a732ec9
parent665c4565ac0dc085b7024eef5965b1bbea17dc74
gtk-shell: Work around non-working startup notifications

GNOME Shell relies on the MetaScreen::startup-sequence-changed signal,
which is tied to (lib)startup-notification and therefore X11. As a result,
when we remove the startup sequence of a wayland client, GNOME Shell will
not be notified about this until startup-notification's timeout is hit.
As a temporary stop-gap, go through XWayland even for wayland clients,
so that the signal is emitted when expected.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=768531
Applied-upstream: no

Gbp-Pq: Name bgo768531_workaround-startup-notifications.patch
src/wayland/meta-wayland-gtk-shell.c