Hello community,
here is the log from the commit of package mutter for openSUSE:Factory checked
in at 2016-11-04 20:50:35
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/mutter (Old)
and /work/SRC/openSUSE:Factory/.mutter.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "mutter"
Changes:
--------
--- /work/SRC/openSUSE:Factory/mutter/mutter.changes 2016-10-18
10:35:30.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.mutter.new/mutter.changes 2016-11-04
20:50:36.000000000 +0100
@@ -1,0 +2,6 @@
+Tue Nov 1 10:09:57 UTC 2016 - zai...@opensuse.org
+
+- Add mutter-fix-startup.patch: Fix slow startup notification for
+ some gtk3 apps when running on wayland (bgo#768531).
+
+-------------------------------------------------------------------
New:
----
mutter-fix-startup.patch
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ mutter.spec ++++++
--- /var/tmp/diff_new_pack.8XQAtY/_old 2016-11-04 20:50:37.000000000 +0100
+++ /var/tmp/diff_new_pack.8XQAtY/_new 2016-11-04 20:50:37.000000000 +0100
@@ -42,6 +42,8 @@
Patch4: mutter-screeenshot-coords.patch
# PATCH-FIX-UPSTREAM mutter-scale-positioner-coordinates.patch bgo#771841
zai...@opensuse.org -- wayland/xdg-shell: Scale positioner coordinates, fix
hidpi menus.
Patch5: mutter-scale-positioner-coordinates.patch
+# PATCH-FIX-UPSTREAM mutter-fix-startup.patch bgo#768531 zai...@opensuse.org
-- Fix slow startup notification on wayland
+Patch6: mutter-fix-startup.patch
BuildRequires: fdupes
BuildRequires: gobject-introspection-devel >= 0.9.5
BuildRequires: libSM-devel
@@ -98,9 +100,9 @@
%package -n libmutter0
Summary: Window and compositing manager based on Clutter -- Library
-Group: System/Libraries
# we need the gsettings schema; hopefully, they'll stay backwards compatible
# (since we can't require = version, to not break SLPP)
+Group: System/Libraries
Requires: %{name}-data >= %{version}
%description -n libmutter0
@@ -143,6 +145,7 @@
%endif
%patch4 -p1
%patch5 -p1
+%patch6 -p1
%build
%configure \
++++++ mutter-fix-startup.patch ++++++
>From 4ed430b4ef3013c96fa56cdc57b925b42d20ead9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuell...@gnome.org>
Date: Thu, 20 Oct 2016 18:00:04 +0200
Subject: [PATCH] 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.
https://bugzilla.gnome.org/show_bug.cgi?id=768531
---
src/wayland/meta-wayland-gtk-shell.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/src/wayland/meta-wayland-gtk-shell.c
b/src/wayland/meta-wayland-gtk-shell.c
index d6e249f..9d1a19e 100644
--- a/src/wayland/meta-wayland-gtk-shell.c
+++ b/src/wayland/meta-wayland-gtk-shell.c
@@ -219,11 +219,21 @@ gtk_shell_set_startup_id (struct wl_client *client,
struct wl_resource *resource,
const char *startup_id)
{
+#if 0
MetaDisplay *display;
display = meta_get_display ();
meta_startup_notification_remove_sequence (display->startup_notification,
startup_id);
+#else
+ /* HACK: MetaScreen::startup-sequence-changed is currently tied to
+ (lib)startup-notification, which means it only works on X11;
+ so for now, always go through XWayland, even for wayland clients */
+ gdk_x11_display_broadcast_startup_message (gdk_display_get_default (),
+ "remove",
+ "ID", startup_id,
+ NULL);
+#endif
}
static void
--
2.9.3
