| Summary: | After upgrade from F24 to F25 xsvreensvaer does not lock the screen | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | J.Jansen <joukj> |
| Component: | xscreensaver | Assignee: | Mamoru TASAKA <mtasaka> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | cheese, mtasaka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:12:53 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: | |
|
Description
J.Jansen
2016-11-28 10:23:22 UTC
Same happens on a fresh-install of F25 + installation of xscreensaver If you are using GNOME, try X, not wayland. I changed my login to GNOME on Xorg but the problem is still there. However is fixed another problem I had : Writeable colour maps using DirectColor visual (i.e. in crystal,swirl and stardish) did not work using wayland but work again with Xorg. Looks like that only switching to X does not help : After a reboot xscreensaver locks the screen. However IMHO it should also work for Wayland.... 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. |