I recently installed Fedora 38 from the standard live .iso with Gnome and out of the box I started encountering some issues after hibernation: every time I hibernate my system (or close the laptop lid) Fedora either doesn’t let me get out of the lockscreen, doesn’t let me get root access in the gnome terminal or crashes as soon as I start an application or open a gnome menu.
This is the log:
I don’t know if there’s a fix available or if it may be useful to the devs, let me know if I’m missing something here to fix this.
When reporting a problem, it is very helpful if you can provide enough detail (hardware platform, update status, using Xorg or wayland, etc.) to allow someone with similar hardware to reproduce the problem (or at least tell you they don’t have the problem, which can help pinpoint the reason).
There are usually some “issues” for fresh installs with things that didn’t get caught in testing, so it is important to install updates. Most uers will hibernate a system with several apps running. It could be useful to see if the problem is specific to one app by closing just one app for each hibernation.
The issue was there on install and updating with dnf didn’t change anything, I don’t really need to open any application to have the OS crash, I just have to close the lid or leave the computer as is until it goes to sleep (guess you can count all the GNOME processess tho). If it can be useful I can install other DEs to see if the issue is GNOME specific.
By the way, I’m using stock Fedora with GNOME and Wayland.
Kindly hoping in your response, let me know if I can provide more info.
Are you using a Gnome Extension for Hibernation? There is an issue in Gnome Shell 44.0 crashing at logout. I wonder if it also affects hibernation. The fix is expected in early June at Gnome Shell 44.2.
hi, I actually made a rookie mistake. I was referring to sleep, not hibernation .
i installed Lxqt and the bug seems to happen either way regardless of Desktop Environment.
Btw, as I said earlier I’m using stock GNOME, no extensions. Systemd is in charge of putting the OS to sleep so it’s either that or even a kernel problem.
Either way I would like for it to be solved, let me know if you guys have any idea of how to solve this.
Kind regards.
This happens to me too since I’ve switched NVMe drives and reinstalled. I can sometimes switch to another TTY via CTRL-ALT-F3 (etc) and see kernel errors during this failure regarding storage. I am using a different NVMe device than you and NOT Intel RAID. But I will actually try switching to another NVMe storage device to see if there’s something wrong with these. I was hoping a kernel update would fix this but it seems like no.
Drives:
Local Storage: total: 476.94 GiB used: 19.03 GiB (4.0%)
ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD
size: 476.94 GiB temp: 36.9 C
The way to solve such problems is to a) make it possible for others to reproduce the issue, and b) provide relevant error messages.
This requires details of your hardware and software, starting with inxi -Fzx and following up when asked for more details. It also requires making sure all available updates have been applied so you are chasing a bug that has already been fixed and so others will be using the same versions. Journalctl provides a wealth of data (more when run with “root” privileges), so there will often be information about a problem buried in a mass of irrelevant data.
Many users try to solve bugs by reinstalling Fedora, switching to an older release, or switching to flatpak versions of a failing application. This is understandable when the user has work they need to do, but means the underlying problem remains open.