Hide Forgot
Description of problem: (1) It is not possible to connect via VNC to the host that is locked (i.e., the host shows the lock screen). (2) Existing VNC connection is terminated the moment the host locks screen. (3) If the host is unlocked (by **physically** logging in), then it is possible to connect via VNC until (2) happens. Version-Release number of selected component (if applicable): server: vino 3.22.0-19.fc33 (Fedora 33, GNOME on X11) client: vinagre 3.22.0-18.fc31 (Fedora 31, GNOME on X11) How reproducible: always Steps to Reproduce: 1. connect to **unlocked** host 2. wait for host to lock screen (or lock screen manually) -or- 1. try to connect to **locked** host Actual results: VNC client is disconnected and cannot reconnect -or- VNC client cannot connect at all Expected results: VNC connection is possible to locked host, VNC connection is maintained in case the host locks screen (so the user can log in again) Additional info: This problem started after upgrading the host from F31 to F33. Built-in screen sharing worked flawlessly in F31. VNC server used before upgrade was vino 3.22.0-16.fc31 (Fedora 31, GNOME on X11). It might be a bug in another component (not in vino).
This is by design, as there is a risk that unlocking remotely could unknowingly present the logged in session to anyone at the physical computer. It can be avoided by running the following two commands in looking glass: global.backend.get_remote_access_controller().inhibit_remote_access = () => {} global.backend.get_remote_access_controller().uninhibit_remote_access = () => {}
Well, I am not happy with this change. Is this solution persistent across reboots? If not, how can I make it run automatically on every reboot (login)? Thanks.
> Is this solution persistent across reboots? If not, how can I make it run automatically on every reboot (login)? It is not. To make it persistent, either it needs to be turned into an extension, or it can be placed in a script that is executed on login. Eventually the plan is to make sure that logging in remotely will not enable the screen on the physical computer, but that is not ready yet.
> Eventually the plan is to make sure that logging in remotely will not enable > the screen on the physical computer, but that is not ready yet. I am looking forward to that. That's how remote desktop works on Windows.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.