From aec3afbd79d0e21a8b2a7e47bea2fd46d0f8cad5 Mon Sep 17 00:00:00 2001

From: Ondrej Holy <oholy@redhat.com>

Date: Wed, 18 Feb 2015 09:03:51 +0100

Subject: [PATCH] Handle closed signal properly on notification prompt

When the notification is closed (e.g. by close button), closed signal

is emitted. This signal isn't handled currently and therefore

vino-server is still waiting for response and block new notification

from client (also doesn't close the connection). Handle close signal

properly to fix this bug.

https://bugzilla.gnome.org/show_bug.cgi?id=744692

---

 server/vino-prompt.c | 10 ++++++++++

 1 file changed, 10 insertions(+)

diff --git a/server/vino-prompt.c b/server/vino-prompt.c

index 85358e1..f99b8e9 100644

--- a/server/vino-prompt.c

+++ b/server/vino-prompt.c

@@ -255,6 +255,13 @@ vino_prompt_handle_response (NotifyNotification *notification,

   vino_prompt_process_pending_clients (prompt);

 }

+static void

+vino_prompt_handle_close (NotifyNotification *notification,

+			  gpointer            user_data)

+{

+  vino_prompt_handle_response (notification, "close", user_data);

+}

+

 static gboolean

 vino_prompt_setup_dialog (VinoPrompt *prompt)

 {

@@ -298,6 +305,9 @@ vino_prompt_display (VinoPrompt   *prompt,

 				  vino_prompt_handle_response,

 				  prompt,

 				  NULL);

+  g_signal_connect (prompt->priv->notification, "closed",

+		    G_CALLBACK (vino_prompt_handle_close), prompt);

+

   g_free (host_label);

-- 

GitLab