Hide Forgot
Description of problem: gnome-shell freezes after screen lock. Can recover only by hard rebooting workstation or by remote ssh login followed by killing the gnome-shell process. Version-Release number of selected component (if applicable): gnome-shell.3.22.2-2.fc25.x86_64 How reproducible: Lock screen manually or leave workstation idle for auto-lock period of 5 minutes. Try to log back into gnome session. Steps to Reproduce: 1. Lock screen of workstation 2. Try to log back in 3. Actual results: Blank screen. Workstation does not respond to keyboard. Expected results: Workstation responds to keyboard input of password, logs into gnome-shell. Additional info: Dell Precision T5500 Workstation running fc25. Bug was not present in fc24 and appeared after upgrade to fc25. good: kernel.4.8.8-200.fc24.x86_64 bad: kernel.4.8.8-300.fc25.x86_64 bad: kernel.4.8.10-300.fc25.x86_64 I already collected dmesg logs, but I am not sure that they reveal the problem. Please advise on what additional information to collect to present as evidence and aid for debugging. Thanks.
I also encounter (very frequent) random freezes when trying to unlock my lenovo T440s running Fedora 25, although it does not appear related to the docking stations. It also seems unrelated to X/Wayland. Concretely: I open my lid, enter my password, press enter, and it never logs in: the login screen completely freezes. I can still move the mouse, but cannot interact with anything anymore. I can still press CTRL+SHIFT+F<number> to switch to a terminal. Once it's frozen, my only solution is to reboot the system. It may have a different root cause than this reported bug.
Have the same problem as Gwendal. I tried to find something useful in the logs, but did not find something relevant. Switching to a terminal, loggin in as a user and restarting gnome-shell with: "killall -SIGHUP gnome-shell" unlocks the screen.
happening here too. But I am on F24 which has been rock-solid for a while but I accepted a bunch of patches in the last 3 weeks and it has been problematic ever since. Some workstation details: Linux xxxxxx 4.10.10-100.fc24.x86_64 #1 SMP Thu Apr 13 01:12:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux some dell desktop precision t3500 24gb ram 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 02:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1) 1 SSD 1 spinnie HD gnome-shell-3.20.4-3.fc24.x86_64 It took me a few days to see that it only happens when I use the screen-lock -- when the screen-lock engages I have a really high likely hood total freeze. If I don't let it engage -- I am good.
Since I upgraded to f26 alpha, I did not encounter the problem. Maybe something upstream fixes everything.
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.
Observed again on F29. # rpm -qa | grep gnome-shell gnome-shell-extension-user-theme-3.30.1-1.fc29.noarch gnome-shell-extension-background-logo-3.24.0-6.fc29.noarch gnome-shell-extension-common-3.30.1-1.fc29.noarch chrome-gnome-shell-10.1-3.fc29.x86_64 gnome-shell-3.30.2-1.fc29.x86_64 Hardware: HP ProBook 650 G3 - CPU: Core i7, RAM: 16 Gb. Really annoying!
I'm also experiencing this problem. The screen freezes after locking it. I'm still able to use the mouse but the clock that is displayed on my lock screen is frozen. The keyboard also doesn't respond anymore and I have to wait a couple of minutes before I can enter my password again. To me that indicates that either my mouse gesture (sliding up) was recognized or pressing escape/enter was recognized, it just takes a while for them to be processed (sometimes up to a minute). $ rpm -qa | grep gnome-shell gnome-shell-3.32.2-1.fc30.x86_64 gnome-shell-extension-launch-new-instance-3.32.1-1.fc30.noarch chrome-gnome-shell-10.1-4.fc30.x86_64 gnome-shell-extension-places-menu-3.32.1-1.fc30.noarch gnome-shell-extension-user-theme-3.32.1-1.fc30.noarch gnome-shell-extension-background-logo-3.32.0-1.fc30.noarch gnome-shell-extension-common-3.32.1-1.fc30.noarch gnome-shell-extension-apps-menu-3.32.1-1.fc30.noarch gnome-shell-extension-window-list-3.32.1-1.fc30.noarch $ uname -a Linux localhost.localdomain 5.1.5-300.fc30.x86_64 #1 SMP Sat May 25 18:00:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cpuinfo | grep "model name" model name : Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz I'm working on a Dell Latitude 7490, 16 GB RAM
Found the core issue. It's NFS. The freeze only occurs when a laptop has some external filesystem mounted via NFS. It happens as follows: I have a NAS server at home, that exports it's FS through NFS. I mount it and, say, browse photo gallery. Then I close my laptop and take it to work. The very first atempt to unlock the screen ends up with the freeze. Obviously, gnome shell tries desperately to access the mounted volume. Workaround: unmount the mounted network volume with 'umount -l'