Hide Forgot
Description of problem: When the desktop has been locked and is being unlocked, displays that are not the primary display with the login form on it, aren't 100% opaque, making it possible to see contours of the underlying windows. I am using Fedora 25 with GNOME3 and the default "wayland" mode after login. This of course, only happens in a multi monitor environment. Version-Release number of selected component (if applicable): I don't know which package is responsible for this but can share additional information on request. How reproducible: Always. Steps to Reproduce: 1. Lock screen 2. Wait for it to shut down 3. Move the cursor or type a key to start unlocking 4. Enable the login form Actual results: Have a look at the other displays and see outlines and shadows of the underlying desktop. Expected results: Do not see any outlines of the desktop. Additional info: Hardware: Lenovo L450 with Intel Corporation HD Graphics 5500, 2 Dell displays attached via display port and daisy chaining. I am not sure if only one of the displays shows any content but can check that later and provide the exact device identifier.
Follow up: I cannot reproduce the error all the time and have not been able to do so after submitting the bug.
This evening, the problem occured again. This time on the main display, after a reboot, displaying the contours of the VirtualBox main window that had been opened on that display before the reboot. I attached a photo and I am still not sure about the responsible component.
Created attachment 1236426 [details] Screenshot
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.