Bug 1258253
Summary: | All windows closed after unlocking screen | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ish37416 |
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | fmuellner, mrgroover, otaylor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 19:17:35 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: |
Description
ish37416
2015-08-30 14:57:38 UTC
I observe something similar. Have you tried switching to another screen when you are going to unlock it? In my case, the lock screen is on Screen 1 (Ctrl+Alt+F1), which gives the conventional login screen where I can select any account. My locked session is on screen 2. When I press Ctrl+Alt+F2 in the lock screen, it is switched over and I can unlock my session. It is then properly restored. So in my case, the lock screen often switches to the first screen, which is the login screen and not the lock screen for my session, which in most cases is on a second screen. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |