Description of problem: In VNC session, after lock screen, when try to unlock, the text window for password would automatically delete user's input and even I type the password fast enough, it still can not unlock gnome. Version-Release number of selected component (if applicable): All software up2date as of today. How reproducible: Always Steps to Reproduce: 1. start vnc session with tigervnc-server $ vncserver 2. connect the vnc session locally use tigervnc and address is: localhost:1 3. GNOME appeared in VNC session, then lock the screen and unlock, it will ask for password to unlock and then found the password I typed there will get deleted automatically and no way to unlock. Actual results: Not able to unlock GNOME Expected results: Unlock GNOME and continue to use Additional info: Not sure if this is a VNC problem or GNOME, the problem only occurs with GNOME in VNC session.
Perhaps the right component is gnome-screensaver.
(In reply to Aaron Lu from comment #1) > Perhaps the right component is gnome-screensaver. Not if you're using the standard GNOME desktop; reassigning.
Same problem under Fedora 25 with GNOME-3.22. I've just reported the problem to upstream, let's see if there is any response: https://bugzilla.gnome.org/show_bug.cgi?id=775066
I always used tigervnc client but today, I tried vinagre and there is no such problems. So I would say this is a bug of the tigervnc client. I had always assumed tigervnc client works best with vnc session created by tigervnc server, looks like this is not the case. I have reassigned to tigervnc.
Since Fedora 25 also has this problem, I changed the version to 25.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.