Linux is cool, I can do a lot of things with it. If i set a config file in Linux, I am damn sure that it is ran every single time. The code does what you tell it to do.

There is 1 thing that always seems to be “black magic”: 1) lid close and suspend 2) lid close and suspend and lock.

If we ignore locking for a moment and focus on suspend. I cant seem to figure out why sometimes lid close would suspend immediately, when other time it takes 5 seconds after lid closes. On some days, lid closes would not even suspend !!

Did anyone manage to get suspend work 100 %? I cant believe we have tons of great linux tools and years into kernel dev, and still suspend is a hit or miss.

  • eldavi@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 hours ago

    i got in the habit of doing this also because suspend didn’t work 100% of the time back then, but stopped when i switched to linux first laptops.

    i switched back to a windows-first laptop recently and forgot about setting it so that it doesn’t auto suspend when i close the lid and it works just fine with fedora on it; linux has made leaps and bounds since the last time i contributed to it.

    although, to be fair, i was on linux-first laptops for a decade so there was plenty of time to catch up. lol