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)
committerJeremy Bicha <jbicha@debian.org>
Sun, 5 Nov 2017 18:03:02 +0000 (18:03 +0000)
commite450bc97b18f7be9dc341829e9a25998a9b4ecc4
tree28e2d8d0324deb158ed0cf70b17cfcbcf72f42a4
parentefbe3db96b3df20af6e62651e2dd83e30b78ad78
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