I dont know if this is pretty common? I reported a bug about this an eternity ago on Fedora, but it is still happening.

I am also not sure what project is responsible, mesa?

Whenever I sleep my Fedora KDE Laptop, close the lid, open it and it turns on but no input works.

Sometimes my entire screen is corrupted too, like this and often only a hard shutdown fixes it, sometimes it reacts by itself.

Do you know something similar? Where should I report it and how can I circumvent this by now, disable S3 sleep?

  • fuckwit_mcbumcrumble@lemmy.worldEnglish
    1·
    11 months ago

    Are you sure S3 sleep is enabled in the bios? On most machines it’s one or the other, not both at the same time. On some Intel machines you can still enable S3 standby, but I know AMD killed it a lot sooner than Intel did.

    Windows has powercfg /availablesleepstates to show what states are supported. I’m sure there’s something like that for linux but I’m not 100% sure. You could try dmesg | grep -i "acpi: (supports"

      • fuckwit_mcbumcrumble@lemmy.world
        2·
        11 months ago

        Microsoft says it’s more secure. and that since it stays on its 100% the OSes control which is supposed to be much more secure”reliable” than S3 standby.

        Nevermind that S0 standby is so incredibly buggy and awful on windows where it’s supposed to be best. My i9 Thinkpad drops 20% battery in 15 minutes, then goes into hibernation. It has a 50% chance of overheating in my bag and crashing when trying to get in to hibernation.