Bug 1081658
| Summary: | Cannot unlock screen since last update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frederic Grelot <fredericg_99> | ||||
| Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | cschalle, rstrode | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-29 19:44:34 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |
Created attachment 879566 [details] journalctl at the time of the error Description of problem: Since the last update+reboot, when my session locks I am unable to unlock it. journalctl shows some errors about my attempts : (see attachement). As you can see : -there are some xscreensaver errors during the lock time (every minute) -I think there is also a problem regarding gnome-keyring... Version-Release number of selected component (if applicable): gnome-session-3.10.1-1.fc20.x86_64 gnome-session-xsession-3.10.1-1.fc20.x86_64 xscreensaver-base-5.26-2.fc20.x86_64 systemd-devel-208-15.fc20.x86_64 systemd-libs-208-15.fc20.x86_64 systemd-python-208-15.fc20.x86_64 systemd-python3-208-15.fc20.x86_64 systemd-libs-208-15.fc20.i686 systemd-208-15.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. start the computer 2. on seat0, log in 3. wait for session lock (10 minutes in my case) 4. move the mouse to unlock Actual results: The screen stays dark, with only the mouse cursor moving Expected results: The screen should propose to enter the password to unlock the station. Additional info: I can still unlock the session using "loginctl unlock-session XX" from another terminal as root. As of this time, is the session locks again, the problem is not exactly the same, but similar : -when I move the mouse, the unlock screen appears -I enter the password, but the unlock screen re-appears as if I should try again (despite the fact that the password was correct, and I wan not told otherwise) -I can still unlock using loginctl. An additionnal info : I am using multiseat (and I am getting more and more problem with it!! Is anybody else using it really???) On secondary seat, I didn't try to reproduce the problem.