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)
committerPeter Michael Green <plugwash@raspbian.org>
Wed, 4 Apr 2018 10:10:12 +0000 (11:10 +0100)
commit42c6312ed67e42bf16317606e751c3af780c45c4
treeff10d7c295c14f978c8b7ba06bdbd6d62301b100
parentb393c253d3800eb9e60dc1d380283db79b44ac22
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