Can't shutdown after suspend on Acer Swift 5 SF514-54T
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't shutdown after suspend on Acer Swift 5 SF514-54T
Hi! I've been having a problem on my Acer Swift 5 SF514-54T laptop where it isn't able to shutdown or reboot after having been suspended at any point during its uptime. It hangs on a black screen and I have to put it out of its misery by manually holding the power button to complete the shutdown. Shutting down and rebooting works perfectly fine if the machine hasn't been suspended since boot. I am running Fedora Silverblue 32. Since I have no idea what could possibly be causing this issue, I'm not sure what other info to provide, so please do ask me if you need any further information. Thanks in advance!
Hey,
I let this one sit a little but before it sinks down I want to reply although I have nothing very helpful to say.
This laptop is pretty new; I think I saw a notebookcheck review from this year, i.e. 2020.
You are currently running one of the few distros that even makes sense on such a new device (Linux always needs a while to catch up with new hardware, but Fedora incorporates new developments very early).
I don't know Fedora but I use ArchLinux, it is another distro that might possibly work on this device.
There's of course the option to hunt down the problem and hope it's solvable.
Start with checking the journal for meaningful messages.
Hey,
I let this one sit a little but before it sinks down I want to reply although I have nothing very helpful to say.
This laptop is pretty new; I think I saw a notebookcheck review from this year, i.e. 2020.
You are currently running one of the few distros that even makes sense on such a new device (Linux always needs a while to catch up with new hardware, but Fedora incorporates new developments very early).
I don't know Fedora but I use ArchLinux, it is another distro that might possibly work on this device.
There's of course the option to hunt down the problem and hope it's solvable.
Start with checking the journal for meaningful messages.
Thank you for your response! This laptop is indeed quite recent, but if possible I'd like to find the problem and report it in order to improve the experience for everyone.
I checked the journal and the last message displayed before the system hangs seems to be from a kernel audit. Another possibly meaningful message I could find is
Code:
pam_systemd(sudo:session): Failed to create session: Access denied
but unfortunately searching on the internet for this string yielded me no useful results.
Same problem there, unfortunately. It hangs on a black screen before completing the shutdown.
OK, then (after a reboot) look at the journal for around that time.
Just show us all the entries from the moment you enter the command.
BTW, you might want to use "poweroff" or "systemctl poweroff" instead.
OK, then (after a reboot) look at the journal for around that time.
Just show us all the entries from the moment you enter the command.
BTW, you might want to use "poweroff" or "systemctl poweroff" instead.
Sorry for the delay - I'm currently traveling, so my Internet connection isn't incredibly reliable. However, I seem to have a pretty stable connection right now, so I put the relevant logs on Pastebin.
Sorry, that is way beyond me.
I went through the output, there's nothing that clearly says "I hang".
Maybe some ACPI problems, you can try some common ACPI troubleshooting methods, temporarily add some command line switches etc.
Maybe gnome-shell crashing has something to do with it, but since the shutdown process continues after that it could only be indirectly.
Of course you're using a bleeding edge distro. Have you looked around their forum?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.