[gnome-remote-desktop] vnc-server: Make refusing VNC clients more explicit
- From: Jonas Ådahl <jadahl src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-remote-desktop] vnc-server: Make refusing VNC clients more explicit
- Date: Mon, 24 Jan 2022 09:52:22 +0000 (UTC)
commit 5f8338ec312e57a64ace948e0b5c4410e1921a70
Author: Pascal Nowack <Pascal Nowack gmx de>
Date: Fri Jan 21 02:28:13 2022 +0100
vnc-server: Make refusing VNC clients more explicit
When refusing a VNC client, due to already having an active VNC
session, gnome-remote-desktop just prints a debug message.
This debug message is by default not visible on the journal.
When users run into situations, where gnome-remote-desktop refuses new
clients, they won't know why they cannot establish a connection
successfully.
To take care of this situation, make this deny-message more explicit by
using g_message(), since this will print the reason for the denial
visibly to the journal without the need of an environment variable.
Closes: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/80
src/grd-vnc-server.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/src/grd-vnc-server.c b/src/grd-vnc-server.c
index 57b8ed2..aae1029 100644
--- a/src/grd-vnc-server.c
+++ b/src/grd-vnc-server.c
@@ -115,7 +115,7 @@ on_incoming (GSocketService *service,
{
/* TODO: Add the rfbScreen instance to GrdVncServer to support multiple
* sessions. */
- g_debug ("Refusing new VNC connection: already an active session");
+ g_message ("Refusing new VNC connection: already an active session");
return TRUE;
}
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]