You are not logged in.
Hi dear fellow-archers,
is anyone else having problems with suspend/hibernate after the current systemd-Update?
For me it stopped working i.e. if I try to suspend or hibernate with a running DE (doesn't matter, if wayland or X11; gtk/qt), the screen turns black and nothing else seems to happen. I have to hard-shutdown my notebook.
If I try to suspend from terminal (e.g. tty3) without login in into any DE, everything works fine (even though a DM is running as a systemd-service. gdm or sddm doesn't matter). Trying to suspend from e.g. tty3 when a DE is running, fails as described above.
As my Notebook has an Intel-GPU, the nVidia-bug should not be the problem (if I'm not wrong).
System:
Lenovo ThinkPad X390 Yoga
Intel® Core™ i7-8565U × 8
Intel® UHD Graphics 620 (WHL GT2)
edit:
I found a part of the problem. But only a part...
as it turned out, this problem only occured with my main-user and only with the kms-hook added.
Removing the kms-hook from mkinitcpio.conf solved the problem.
But the questions still remaining are:
why does it only affect my main-user-account and why did this problem just appear a few days ago without me consciously changing my user configuration...
Last edited by Koile (2024-09-30 13:39:44)
Offline
Read 7.2
https://wiki.archlinux.org/title/Power_ … _hibernate
Since the last update I've done. When suspending from WM/DE, upon wake the machine wakes for 3 seconds and then re-suspends, every time. It will wake normally on the second try. All of my (all intel) machines using modesetting do that. An old one using xf86-video-intel and mesa-amber wakes normally. Backing out of X and suspending solves the other machines. Wake up and startx.
I haven't downgraded the kernel. I'm going to leave it until next update.
Welcome to arch. Constant updating sometimes causes bugs to show up. If you don't like how arch works, wait until the next update, it'll change.
The wiki is the first place to look with bugs like that.
Offline