Created attachment 1232540 [details] core_backtrace Description of problem: With some configurations, GNOME Shell crashes on screen unlock, causing a long delay (15+ seconds) before the screen actually unlocks and the desktop is usable again Version-Release number of selected component (if applicable): gnome-shell-3.22.2-2.fc25.x86_64 glib2-2.50.2-1.fc25.x86_64 How reproducible: On my work configuration, this is reproducible. When I take that same laptop home and use it in a different configuration, this does not occur. Work configuration (problem occurs): Docked Thinkpad W541, connected to an AOC 27" display (2560x1440) over displayport. Both the built-in display (secondary) on the laptop and the external display (primary) are on, with the external display rotated to be long rather than wide. Home configuration (problem doesn't occur): Thinkpad W541 not in dock, connected to an external display (1920x1080) over mini displayport. In this configuration, the external monitor (primary) is not rotated, and is usually the only active display (sometimes the built-in display is active as a secondary). Steps to Reproduce: 1. Have a configuration like mine or possibly some others 2. Lock the desktop and wait for it to go dark (gnome-screensaver?) 3. Enter password to unlock the desktop, experience the issue Actual results: Long wait Expected results: No wait Additional info: ABRT sez "Reporting disabled because the backtrace is unusable", and in the attempted report generation output I see "Duplicate bugzilla bug '#1402492' was found". Given that abrt won't create the bz (and I think I've heard Adam Williamson say "abrt isn't always right" in other bugs?), here's some of the details from the 'details' pane from there (I don't know what's useful): reason: gnome-shell killed by SIGTRAP package: gnome-shell-3.22.2-2.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 architecture: x86_64 kernel: 4.8.13-300.fc25.x86_64 uuid: 49274f269fdae4ec4af55d12bf67a5f4caef541a
Retrace link according to abrt: https://retrace.fedoraproject.org/faf/reports/1375442/ Potential duplicate according to abrt: bug #1402492 coredump file: https://galileo.fedorapeople.org/rhbz1405392-coredump
I have found this happens after a screen blank after roboot before I log in.
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.