Indeed, I see absolutely no reason to disable suspend on unknown machines. It works on the vast majority of hardware out there, and if it doesn't, then you'll learn to "just don't do that" on that particular machine. But it seems wrong to arbitrarily and unnecessarily break such an important functionality.
Disabling it on known-broken machines indeed seems to be a better way to go, although it'd be even better to actually fix it on these machines :) For many older machines we can apply quirks in pm-utils. Such a blacklist would be most suitable to maintain in pm-utils, from where upower will pick it up through pm-is-supported reporting False for the respective operation (suspend/hibernate). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812394 Title: Disable suspend/hibernate options when they are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/812394/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
