On Tue, 2019-09-03 at 16:41 +0200, Kamil Paral wrote:
> I use Remmina to connect via VNC, and it works.
> But when the system, after the default 5 minutes of inactivity
> blanks
> the screen and locks the user session, VNC session is terminated.
Can you re-connect and unlock the session?
No. In reality I've seen that the screen is stuck. Remmina is still
connected, but I can only see the background with the clock (freezed).
While the machine has the cursor arrow and the black background.
If I disconnect the VNC session and I try to reconnect, it times out.
> While on F30 the VNC session is not terminated even if the
screen
> goes
> blank and the session is locked; I can unlock the session via VNC.
Do you use X11 in both releases? I don't know if Wayland can already
work with VNC through Pipewire, so just checking.
No no, it is Wayland.
> I tested it on bare metal and in a KVM VM.
> In addition, when I try to unlock the session, on the bare metal
> machine the cursor arrow appears, but the screen stays black and
> the
> mouse and the keyboard don't work.
You mean unlocking by re-connecting VNC, or unlocking locally? Does
this happen only after the VNC use case, or always?
Oh yes, sorry, I mean unlocking locally. And it happens only if I was
connected via VNC.
> I would like to wait the GNOME mass rebuild before filing a bug
(if
> it
> wasn't already filed by someone else).
If you continue to see it after the rebuild, please file bugs and
possibly even propose them as blockers. "Screen sharing" is one of
the options in gnome-control-center, so it's expected to work
reasonably well. Screen unlocking even more so :-)
Sure.
Thanks. :-)
A.