Fedora suspend wakes up immediately
from dr_sentinel@lemm.ee to linux@lemmy.ml on 25 May 18:32
https://lemm.ee/post/64973308

Fedora 42 gnome, suspend does not work it wakes up immediately and stays in the login screen.

#linux

threaded - newest

enemenemu@lemm.ee on 25 May 18:48 next collapse

Via cli?

dr_sentinel@lemm.ee on 26 May 18:00 collapse

via cli also has same issue

catloaf@lemm.ee on 25 May 18:59 next collapse

What’s in the logs?

sasquash@sopuli.xyz on 25 May 19:04 next collapse

I have the same issue but with KDE. But in my case I think its because of the wireless mouse.

just_another_person@lemmy.world on 25 May 19:09 next collapse

Check dmesg and system logs and post relevant entries.

dr_sentinel@lemm.ee on 26 May 17:58 collapse

pastebin.com/ZsZ8MguP

just_another_person@lemmy.world on 26 May 19:43 collapse

I saw your comment that you don’t have swap enabled, and you’re trying to hibernate. This won’t work. Create a swapfile equal to your memory size.

linuxize.com/post/create-a-linux-swap-file/

dr_sentinel@lemm.ee on 27 May 17:56 collapse

hey im trying to suspend not hibernate.

just_another_person@lemmy.world on 27 May 18:14 collapse

The resume message suggests otherwise…

Are you POSITIVE your BIOS supports S3 and not S4?

dr_sentinel@lemm.ee on 28 May 12:59 collapse

im not sure, it shows [s2idle]. however my laptop used to succesfully suspend in arch, ubuntu and windows when i used them few months back. this week ive tried mint and fedora and both have this issue. as another person here said i think its a kernel issue

0xf@lemmy.ml on 25 May 19:10 next collapse

Try to turn off ‘fast boot’ in bios and test again, should work.

dr_sentinel@lemm.ee on 26 May 06:56 collapse

Not working :(

Father_Redbeard@lemmy.ml on 25 May 19:11 next collapse

Do you have a Gigabyte motherboard in your PC? I’m battling the same with Pop!_OS that is related to Gigabyte mobos of a certain model. There is a fix, but I havent been able to get it to work and haven’t had time to find out why.

Specifically the B550 model(s).

dr_sentinel@lemm.ee on 26 May 06:59 collapse

I have an acer aspire lite AL5141. But suspend used to work in arch. Im thinking of using previous kernel version maybe that will fix.

Karkitoo@lemmy.ml on 25 May 19:13 next collapse

Did you have Firefox running perchance ?

It happened often to me so it became a habit.

terminhell@lemmy.dbzer0.com on 25 May 19:42 next collapse

Is it just f42 or any OS? I’ve had issues in the past with some mice being treated as a keyboard and it would do exactly this.

dr_sentinel@lemm.ee on 26 May 06:49 collapse

Fedora & mint has this issue, but suspend works in arch tho. Maybe because i dont have swap partition?

terminhell@lemmy.dbzer0.com on 13 Jun 22:46 collapse

Maybe you’ve fixed this by now, but thinking about it again it was a gaming mouse I used to have. Windows would do it too. Ended up having to do something with it in dbus or something cuz it reported as a keyboard instead of a mouse.

Kambo@lemmy.world on 25 May 19:55 next collapse

Hope this will help.

I fixed this issue by disabling USB Wake up for my mouse. The wireless receiver/mouse seemed to be sending a constant request to wake up the computer, so obviously, when put to sleep, it would wake up immediately.

that_leaflet@lemmy.world on 25 May 21:35 next collapse

This also also affecting me. Though it was just because I was unaware of the USB wake function. Since I have, I made it a habit to suspend, then immediately lift up my mouse to turn it off. Though I guess that’s not an option for wired mice.

dr_sentinel@lemm.ee on 26 May 06:36 collapse

Didnt solve for me :(

pemptago@lemmy.ml on 26 May 07:40 next collapse

Had a similar problem on Pop_OS. Seemed to be an nvidia diver issue. Suspend would stop working after a driver update and sometimes go away after another update. This happened 2 or 3 times. There were also some logs about nvidia suspend issues. My troubleshooting was unsuccessful and iirc, it was complicated to keep pop from updating so I eventually swapped nvidia for amd and it stopped being an issue.

dr_sentinel@lemm.ee on 26 May 10:32 collapse

i already use amd tho

pemptago@lemmy.ml on 26 May 17:21 collapse

Shoot. Sorry I couldn’t help then. Good luck with your troubleshooting. I know it can be a very frustrating issue.

oranki@sopuli.xyz on 26 May 12:14 next collapse

I’m not sure if this is of any help, but I had the same issue with Wake on LAN enabled. This was a while ago with an Asus motherboard.

If you don’t need WoL, disable it and it should fix it if your MB is affected.

But if you do need WoL, look at wiki.archlinux.org/title/Wake-on-LAN.

The section 5.2.2 Fix by kernel quirks was what fixed it for me.

ArsonButCute@lemmy.dbzer0.com on 26 May 13:22 next collapse

Please confirm that sleep is configured correctly for your hardware.

Read this article from the Arch Wiki then refer to Section 3 after you’ve familiarized yourself with the content to make the changes necessary.

Many hardware implementations of the various sleep types are borked due to workarounds for the way Windows would prefer to handle sleep. The information in this article should allow you to mitigate this.

MangoPenguin@lemmy.blahaj.zone on 26 May 16:27 next collapse

My HP laptop did that until I disabled “Deep Sleep” in the BIOS settings, now it sleeps properly and only loses a couple percent per day.

dr_sentinel@lemm.ee on 26 May 17:50 collapse

Theres nothing like deep sleep in my acer bios

MangoPenguin@lemmy.blahaj.zone on 26 May 18:06 collapse

Check what the last wake source was and see of that helps.

IanTwenty@lemmy.world on 26 May 17:23 collapse

The logs should indicate the device/app that prevents suspend, run ‘journalctl -r’ after it happens.There are ways to disable devices from preventing suspend but we need to know what’s causing it first.

dr_sentinel@lemm.ee on 26 May 17:50 collapse

here is the output pastebin.com/ECXUuBKm

IanTwenty@lemmy.world on 26 May 18:46 collapse

Your IRQ ‘permission denied’ log lines could be caused by this: github.com/Irqbalance/irqbalance/issues/336

…to which the answer is currently to wait for kernel fix. Whether this is the cause of the suspend issue as well I couldn’t say.

Is this all the logs, from very start of you hitting suspend to when the machine comes back? I ask because I expected to see more things stopping and then restarting…