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)
committerIain Lane <laney@debian.org>
Thu, 29 Nov 2018 17:29:57 +0000 (17:29 +0000)
commitba67bc8f394a110b22f9fe6bbb129d08ed678625
tree0482e80d24d7b990581a785cc64f2bc8fb131398
parentaee341f7a15a1343d166dd83937c1f42c0e7c79b
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