Unfortunate effect when running in full screen and the connection drops

20 views
Skip to first unread message

Per Weijnitz

unread,
Sep 2, 2022, 1:36:01 PM9/2/22
to turbovn...@googlegroups.com
Hi,

I always run the turbovnc client in full screen mode. When the network connection to the server drops for different reasons, I cannot interact with the desktop system anymore, because the frozen fullscreen turbovnc client is in the foreground, and somewhere behind it, hidden from sight, is the "Connection dropped, reconnect?"-dialog. The window manager I use does not permit me to swap the window out neither, so my options are:
 1. ssh to the client machine and kill the turbovnc process
 2. press Ctrl-Alt-Function key to drop into a tty, login and kill the process
 3. reboot the machine with the power switch

It would be really useful if the turbovnc client dropped out of fullscreen mode when it opens the "Connection dropped, reconnect?"-dialog.

Finally I would like to take the opportunity to say THANKS for a fantastic program - it has really improved my ways of working!

Best regards
Per

DRC

unread,
Sep 2, 2022, 2:49:18 PM9/2/22
to turbovn...@googlegroups.com
I assume you're using Linux, since you said "window manager."  I will
look into it.

DRC

unread,
Sep 7, 2022, 5:45:55 PM9/7/22
to turbovn...@googlegroups.com
I am unable to reproduce the issue.  Which window manager are you
using?  Can you confirm whether passing -nograbpointer to vncviewer
works around the issue?  If so, then I probably just need to modify the
exception handler so that it disables pointer grabbing before displaying
an error/warning dialog.

DRC

On 9/2/22 12:35 PM, Per Weijnitz wrote:

DRC

unread,
Sep 30, 2022, 12:10:07 PM9/30/22
to turbovn...@googlegroups.com
Please answer the questions so I can diagnose the issue.  Thanks.

DRC

DRC

unread,
Nov 14, 2022, 12:41:07 PM11/14/22
to turbovn...@googlegroups.com

In case others stumble upon this issue, the user confirmed that setting _JAVA_AWT_WM_NONREPARENTING=1 in the environment worked around the issue.  Apparently the issue is another facet of https://github.com/TurboVNC/turbovnc/issues/337.

On 9/2/22 12:35 PM, Per Weijnitz wrote:
Reply all
Reply to author
Forward
0 new messages