Created attachment 1698104 [details] journalctl output from when the crash ocured Description of problem: On my Dell Latitude 5590 laptop fedora freezes as soon as the screen is locked and blank (turned off). This happens almost deterministically, about 95% of the time. It does not happen on my MSI laptop. Version-Release number of selected component (if applicable): How reproducible: Most often, but only on specific hardware. Steps to Reproduce: 1. From gnome (logged in), lock the screen 2. Screen gets blank, wait 10 seconds 3. Press a key or move the mouse to activate the screen again Actual results: Screen does not get activated, stays black. Cannot use Ctrl+Alt+F4 either to get to a different console. Pressing the power button has no effect, computer needs a hard reset to start again. Expected results: Screen gets bright again and I need to enter my password to unlock it. Additional info: I honestly have no clue which component is really causing the issue here or whether it is fedora specific. I do not know how to debug this issue, but it makes my life quite miserable as I cannot simply close my laptop and bring it to another room. Instead I always need to power cycle. Attached is a journalctl output from right before I pressed and held the power button to turn off the laptop. If there is more useful information to provide, just tell me, the issue is easy to reproduce.
Does it reproduce with https://bodhi.fedoraproject.org/updates/FEDORA-2021-453df8d9ee applied? Are you using the Wayland or X11 session? If the former, can you add 'MUTTER_DEBUG=kms' into your environment (e.g. /etc/environment), reboot, reproduce the issue, and attach the output from journalctl /usr/bin/gnome-shell
I cannot apply the update you linked. That is for Fedora 34, and I am still on 33. It seems like there is no corresponding version of gjs available for Fedora 33 yet. I am using Wayland and applied the line you mentioned to /etc/environment. The output from 'journalctl /usr/bin/gnome-shell' for the last 3 boots is attached. The boot at 'Mar 24 16:09:51' is the one that crashed. I had to press and hold the power button to shut off the system. To me, it does not look much different from the current boot or the one before, which was a regular reboot (to make the change in /etc/environment effective).
Created attachment 1765828 [details] journalctl output for /usr/bin/gnome-shell
Ah, sorry, didn't notice this was not for F34. I wonder if you're running in to the same issue as described in https://bugzilla.redhat.com/show_bug.cgi?id=1900890. The output from `journalctl -k` could possibly be useful.
Thanks for pointing to that bug report. I had a look at it, but my issue seems different. When my system crashes, then it is dead and I cannot ssh into it. Also, when I suspend, then the power button stays illuminated. Now I just noticed something strange: Earlier today I could suspend and wake up correctly multiple times. Those times the power button turned off when suspended. "Luckily" I was able to "fix" this by a regular reboot. Now it crashes again on suspend, reliably. `journalctl -k -b -1` is attached. This is from a run where I tried to suspend after loging in to gnome and it crashed and I had to power cycle.
Created attachment 1766116 [details] journalctl -k
Are you saying it *crashes* (returns to login screen, coredump listed in coredumpctl), or *freezes* (screen gets stuck, can't move mouse, can't switch TTY)? If it's the latter, and you can't access via ssh either, it's a kernel freeze, and we should probably move it to the kernel.
My laptop freezes. After locking, the screen fades to black and then remains black forever. Can't switch TTY, can't ssh anymore. Existing ssh connections freeze. So yes, moving to kernel would be good. I also tried adding "i915.modeset=0" to the kernel parameters on grub. This allows me to suspend and wake up again. Well, after wakeup the screen remains black, but I can ssh in and when I type my password I can login and shutdown via keyboard. Also, I just upgraded to Fedora 34 Beta and have gjs 1.68.0 now, but that did not help.
Yea, if your whole computer freezes, including ssh connections etc, any gjs or gnome-shell update are unlikely to make a difference, as it's a kernel freeze. Lets move this to the kernel.
I did report this problem upstream for the intel graphics driver, as I suspected it to be the culprit: https://gitlab.freedesktop.org/drm/intel/-/issues/2404 But the answer did not help me much. I am not a kernel developer and do no know how to just apply some kernel code from some repository.
Maybe a hardware bug, maybe not, I decided to give up on this and simply live with the fact that I cannot suspend my laptop. I will remember not to close the lid when going to present something and be done with it. For details see the upstream bug on https://gitlab.freedesktop.org/drm/intel/-/issues/2404 If the problem affects somebody else, feel free to reopen or file a new bug. Thanks for everyone who read this and tried to help, I appreciate it.