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)
committerMarco Trevisan (Treviño) <marco@ubuntu.com>
Thu, 24 Jan 2019 18:00:14 +0000 (18:00 +0000)
commit5b4fb6480870cdd0c3944210d503bed90239add2
treefaa2aead93a65351eb963379a7f4ca92bdc63db0
parent7cd1ffd7c14aa49cc3a02644b1b707d24f79b8b3
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