Created attachment 1765013 [details] journalctl output at the time of crash Description of problem: When computer is left unused and gets locked, and if it remains locked for more than 3-4 mins, on unlocking (entering password and pressing Unlock button, gnome shell crashes. On Xorg session, it restarts in place and system has to be unlocked again. On Wayland, it throws user back to GDM. Version-Release number of selected component (if applicable): gnome-shell-40.0~rc-1.fc34.x86_64 How reproducible: Lock the machine and leave for 5 mins. Try unlocking. Steps to Reproduce: 1. Lock the machine or let it lock itself after timeout 2. Press any key to wake up screen and show Gnome lock screen. 3. Enter password and press return key or click Unlock button. Actual results: Gnome shell crashes and ABRT notification displays. On XOrg, shell is relaunched and lockscreen is displayed again. Unlocking works this time. On Wayland, GDM login screen gets displayed. Expected results: System gets unlocked and ready to work without any crashes. Additional info: I tried creating a new user and tried in that account and also reset all Gnome settings in my account by using dconf reset -f /org/gnome. But the problem is not resolved. As per journalctl log, crash is happening in Gnome Shell in a libgjs.so function. Log is attached for reference.
Proposed as a Blocker for 34-final by Fedora user krazyabouttechnology using the blocker tracking app because: Gnome shell is crashing whenever machine is unlocked. Being a core component and a primary use case on a primary desktop environment, it should be fixed before release.
This has started happening after the upgrade from Gnome40.beta.0 to rc.0, before that it was working fine. This is an upgraded system from Fedora 30 till now, so it could be a residual package or config issue as well. But upgrade from F33 was totally successful and it ran fine for almost all the time when we were on Gnome 40 alpha and beta. I upgraded on the few days before beta freeze. There are no extensions installed, in fact extensions are turned off, the user account is brand new and minimum configuration changes have been done via Settings app and gnome-tweak-tool.
It seems the latest version of gjs package released few hours back to updates-testing fixed it. Will keep under observation for a day and close if all works fine.
*** This bug has been marked as a duplicate of bug 1940171 ***