At least in my testing, IdleSinceHint is 0 for the SSH sessions that the
TurboVNC Viewer creates for tunneling, so I doubt that any of those
sessions would stop the suspend. Also, the SSH sessions (and associated
logind sessions) created for tunneling only persist while the TurboVNC
Viewer is connected. If the TurboVNC session is started using the
TurboVNC Session Manager, then it will have a separate logind session
that persists for the life of the TurboVNC session, but that logind
session remains in the "Closing" state.
TigerVNC actually does have a logind session associated with the
TigerVNC session. However, that comes at a steep price. You can't have
multiple simultaneous TigerVNC sessions (or a TigerVNC session and a
local session), you have to start all TigerVNC sessions as root, and you
have to statically assign a display number to each TigerVNC session (one
per user.) Also, TigerVNC doesn't appear to set IdleSinceHint either.
TurboVNC's multi-session capability is a result of creating an
independent D-Bus session bus instance for every TurboVNC session. It
may be possible to feed idle state information back to the SSH session's
logind session, but I strongly suspect that we couldn't do that unless
we used the logind D-Bus session bus instance. You can make a TurboVNC
session use the logind D-Bus session bus instance by setting
TVNC_USERDBUS=1 in the environment, but it subjects you to the same
single-session limitation of TigerVNC (although not the other
limitations, so the TurboVNC Session Manager would still work.)
Sorry I don't have any good ideas. My knowledge of systemd is very limited.
DRC
On 1/3/25 2:26 PM, 'Felix Natter' via TurboVNC User Discussion/Support
wrote:
hello DRC,
thank you for looking into this issue! A colleague and I tried the
setup again (we are both in HO),
and we also cannot see a login session generated by (turbo-)VNC.
Probably this is never generated,
and we were wrong :-/
Are you saying that a TurboVNC session that uses ssh tunneling likely
would stop the suspend
when working in the VNC session? Is there any other way to create a
login session from VNC?
Many Thanks and Best Regards!
Felix
Am Fr., 3. Jan. 2025 um 17:30 Uhr schrieb 'DRC' via TurboVNC User
Discussion/Support <turbovnc-users@googlegroups.com>:
I can't make the TurboVNC sessions show up with 'loginctl
list-sessions' at all. The only thing I see in that list are GDM
and the SSH sessions, so there will be a login session associated
with a TurboVNC session only if there is an active connection to
that TurboVNC session that uses SSH tunneling.
What am I doing wrong? I tried on both Rocky and Ubuntu.
DRC
On 12/21/24 7:05 AM, 'Felix Natter' via TurboVNC User
Discussion/Support wrote:
Dear turbovnc developers/users,
dear DRC,
we are using systemd-logind's suspend mechanism for setting idle
computers
to sleep. This works with ssh and physical sessions, but not with
(T)VNC
sessions (the vncserver computer will go to sleep even if you are
interacting
with the desktop in the VNC session).
You can see this when the "IdleSinceHint" of the tvnc session
does not update:
$ enable logind automatic suspend (/etc/systemd/logind.conf):
IdleAction=suspend
IdleActionSec=30min
$ systemctl restart systemd-logind
$ loginctl list-sessions
$ loginctl show-session <id> -p IdleSinceHint
I could use systemd-inhibit(1) on the vncserver instance,
but I would like to reuse the tvnc session also in the
office. Of course I can run systemd-inhibit on *any* process
that runs all day, but I would like to have a more automated
solution :-)
Do you have any idea/solution?
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 visit
https://groups.google.com/d/msgid/turbovnc-users/CAPBq%2BwYNm9vC8mf8oLBLLy73eh7Rw9BwcxD9qB0eCYJtcGfevA%40mail.gmail.com
<https://groups.google.com/d/msgid/turbovnc-users/CAPBq%2BwYNm9vC8mf8oLBLLy73eh7Rw9BwcxD9qB0eCYJtcGfevA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
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 visit
https://groups.google.com/d/msgid/turbovnc-users/4e3c5b3d-fcda-4fc8-8b0e-ddc096faf897%40virtualgl.org
<https://groups.google.com/d/msgid/turbovnc-users/4e3c5b3d-fcda-4fc8-8b0e-ddc096faf897%40virtualgl.org?utm_medium=email&utm_source=footer>.
--
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 visit
https://groups.google.com/d/msgid/turbovnc-users/CAPBq%2BwY9BGAPTXMyRK72djhn7g2NjtN9oGf1%2B7W8dJew%2BAnurg%40mail.gmail.com
<https://groups.google.com/d/msgid/turbovnc-users/CAPBq%2BwY9BGAPTXMyRK72djhn7g2NjtN9oGf1%2B7W8dJew%2BAnurg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
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 visit
https://groups.google.com/d/msgid/turbovnc-users/d6d08fdd-874c-47ed-90db-caf163b38e21%40virtualgl.org.
