Package: gnome-shell Version: 3.22.3-3 Severity: important Sometimes when the laptop lid is closed it doesn't really go to sleep. Sometimes after opening it the desktop doesn't come back, just a black screen or flickering screen.
In one instance, after opening it again, it was observed that the X screen (tty2) was black and flickering every few seconds. Pressing CTRL-ALT-F1 showed the X screen (tty1) for a new user login but pressing CTRL-ALT-F2 again went back to the flickering screen. I was able to log in on tty3 and run journalctl, it found this: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) I searched for that in a search engine and found this: https://bugzilla.redhat.com/show_bug.cgi?id=1401382 Checking the memory usage of the gnome-shell process I found it was at 400MB. I tried to kill it and it wouldn't stop. Then I used kill -9 and it stopped and a few moments later a new gnome-shell process was started and I was able to use the system again, all the desktop windows were still present as they were before. I've saved a copy of the full journalctl output from the day when this happened. At the time when I closed the log includes a few errors: org.gnome.Shell.desktop[1797]: Window manager warning: Failed to set power save mode for output eDP-1: Permission denied 17:14:06 gnome-shell[1797]: JS ERROR: TypeError: item is undefined 17:14:06 NMConnectionDevice<._activeConnectionChanged@resource:///org/gnome/shell/ui/status/network.js:388 wrapper@resource:///org/gnome/gjs/modules/lang.js:178 17:14:09 systemd-sleep[16824]: Suspending system... and about 20 seconds later more messages about, like this: 17:14:29 kernel: PM: Preparing system for sleep (mem) but I think those started appearing after I opened the lid again because it wasn't really sleeping. Regards, Daniel