hello DRC,

regarding 1)
ok, I will test "-listen local", but unfortunately, I cannot do this 
short-term.

> regarding https://github.com/TurboVNC/turbovnc/issues/238:
> loginctl unlock-session does not work for me.

I have another solution for unlocking the session if it is blocked,
but it is annoying since we have the policy to lock the session after 2mins.

> I am still unable to reproduce the issue, and I can't imagine why running 
the Flashback session would matter.  Flashback just puts a GNOME 2-style 
GUI on top of the GNOME 3 shell.  It's still GNOME 3 under the 

Flashback vs. GNOME3 seems to do things a little differently. I observed 
that
if I unlock a Flashback VNC session ("HO"), it will not unlock the GNOME3 
session ("office"),
which is the bug that I wanted to avoid with this post :)

> hood.  I would love to figure out why the issue is occurring on your 
system, because it might reveal a deficiency in TurboVNC that needs to be 
addressed.  Any chance you could send me the TurboVNC Server log > 
> from a TurboVNC session that was killed whenever you logged out of the 
local session?

Here is what I did:

- create server :2 on HOSTNAME
- log out session on HOSTNAME
- connect to HOSTNAME:2 from B (another network: B can access HOSTNAME but
  not the other way around)

Now the VNC session is unusable:
"Could not connect: Verbindungsaufbau abgelehnt. Attempt to reconnect?"

" Verbindungsaufbau abgelehnt" is probably "connection refused".

see hostname.log (probably not of much help).

If I start the server HOSTNAME:2 from a localhost ssh session and log out,
then I can connect to the session, but cannot unlock it when it is locked.

Many Thanks and Best Regards,
Felix

-- 
You received this message because you are subscribed to the Google Groups 
"TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to turbovnc-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/turbovnc-users/234c0964-7f10-4da9-a1ed-a657708130e1n%40googlegroups.com.
TurboVNC Server (Xvnc) 64-bit v3.1 (build 20231117)
Copyright (C) 1999-2023 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

08/01/2024 05:51:57 Using security configuration file /etc/turbovncserver-security.conf
08/01/2024 05:51:57 Enabled security type 'tlsvnc'
08/01/2024 05:51:57 Enabled security type 'tlsotp'
08/01/2024 05:51:57 Enabled security type 'tlsplain'
08/01/2024 05:51:57 Enabled security type 'x509vnc'
08/01/2024 05:51:57 Enabled security type 'x509otp'
08/01/2024 05:51:57 Enabled security type 'x509plain'
08/01/2024 05:51:57 Enabled security type 'vnc'
08/01/2024 05:51:57 Enabled security type 'otp'
08/01/2024 05:51:57 Enabled security type 'unixlogin'
08/01/2024 05:51:57 Enabled security type 'plain'
08/01/2024 05:51:57 Desktop name 'TurboVNC: HOSTNAME:2 (fnatter)' (HOSTNAME:2)
08/01/2024 05:51:57 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
08/01/2024 05:51:57 Listening for VNC connections on TCP port 5902
08/01/2024 05:51:57   Interface 0.0.0.0
08/01/2024 05:51:57 Framebuffer: BGRX 8/8/8/8
08/01/2024 05:51:57 New desktop size: 1240 x 900
08/01/2024 05:51:57 New screen layout:
08/01/2024 05:51:57   0x00000040 (output 0x00000040): 1240x900+0+0
08/01/2024 05:51:57 Maximum clipboard transfer size: 1048576 bytes
08/01/2024 05:51:57 VNC extension running!
xstartup.turbovnc: Creating new session bus instance:
xstartup.turbovnc:   unix:abstract=/tmp/dbus-dOwEvQoqmS,guid=85eed2a1af3c6427861a997f659b7f6e
xstartup.turbovnc: Using 'ubuntu' window manager in
xstartup.turbovnc:   /usr/share/xsessions/ubuntu.desktop
xstartup.turbovnc: Executing /etc/X11/Xsession "env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu"


Reply via email to