-7

Broken Suspend on Linux is a Bigger Problem that You Think (lemmy.nz)

submitted 1 week ago* (last edited 1 day ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world

2 comments fedilink hide all child comments

TLDR: Linux doesn't warn you about broken suspend because the DEs can't detect it, the kernel won't admit it, and the culture refuses to acknowledge vendor-caused hardware risks.

There is potential for hardware damage that Linux doesn't warn you about, because the ecosystem is built on assumptions that make warnings politically, technically, and socially "impossible" for the people who maintain DEs despite the developers knowing better. -More about potential damage to hardware from 'comes with no warranty' software: ⚠️Linux/FOSS can damage hardware or firmware

NVMe drives can overheat during broken suspend loops. Fans can run at 100% while the system thinks it's asleep. VRMs can stay powered without proper throttling. GPUs (especially Nvidia) can fail to reinitialize and lock in high-power states. Wi-Fi/BT chips can get stuck in undefined firmware states... AND battery controllers can misreport charge and degrade faster.

-These are documented kernel regressions, bug reports, and vendor advisories.

Linux DEs cannot reliably detect when suspend is broken, so they're stuck with the worst possible situation in not being able to warn you. A warning would imply liability, and Linux developers refuse to own vendor failures: If GNOME or KDE added a warning like: "Suspend may damage your hardware," They would immediately be blamed for fearmongering, breaking user trust, making Linux look unstable, and scaring new users. (The GNU/GPL cult acts like a bunch of psychopaths and will down-vote important information like this as they historically do).

Linux culture strongly resists nagging or hand-holding. The culture believes that Linux users should know what they’re doing, and if suspend breaks, they're supposed to file a bug report. They don't want Windows style popups warning them, or any clutter to the UI. They also don't want to 'scare' people from Linux (Yet when secrets come out -boom: you get subs like communities like Linuxsucks!)

Linux has a long history of exposing features even when they're broken. Suspend is just another casualty of their idiotic philosophy.

Linux DEs don't have the manpower, the vendor cooperation, or the infrastructure to maintain a global database of suspend reliability. So, they: Show the option and hope the kernel handles it.

**"What do you expect for free?"

you are viewing a single comment's thread
view the rest of the comments

this post was submitted on 24 Aug 2026

-7 points (11.1% liked)

Linuxsucks

405 readers

94 users here now

For knowledge and awareness about what using Linux is really like and pointing at its cultish toxic community. We also cover FOSS /FLOSS failures, and issues with GPL since it relates to Linux. Moderation is heavy handed to appeal to our target users.

Rules:

FOSS (especially GPL) advocates and Linux (specifically GNU/Linux) evangelists aren't welcome (GNU Hurd will count as Linux). -We ask that you block us and we will perma-ban for violations of this rule.
Try to stay on topic (that is LINUXSUCKS!). No bashing other OSs or each other. We aim for a cohesive non-toxic community with the interest of cautioning people / would be victims from Linux. At our discretion, we will remove what we consider pollution.
Moderators run the sub, not the users. It's not democratic, and we don't care how you think it should be run. -Feel free to make and run your own community.
"Not your Billboard" -Over-represented companies will have positive posts removed and appropriate bans may be issued. -Those companies included so far will be Valve/Steam/Proton, Google, and Brave (browser).