@Jérôme, Regardless of how you go about it, you'd need to enter a complex passphrase each time you start your computer, whether it's a cold boot or after hibernation.
To give a comparison, imagine if Windows introduced a security feature requiring every user to enter a complex passphrase when turning on the computer; furthermore, every user on a single computer would need to know the same shared passphrase (in addition to their own login password). There would be a worldwide revolt. Ubuntu would have the very same restrictions. That's why hibernation cannot reasonably be available by default; the majority of Ubuntu users are not technically expert, but rather are "everyday" users and would revolt against this. Full-disk encryption is available via LUKS (now an option during installation in 13.10) for those who have the need, and hibernation can work then; perhaps it should be available by default, but only when LUKS is being used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/812394 Title: Disable hibernate option by default Status in Ayatana Design: Fix Released Status in Pantheon Session Indicator: Invalid Status in PolicyKit: Invalid Status in “policykit-desktop-privileges” package in Ubuntu: Fix Released Status in “policykit-desktop-privileges” source package in Precise: Fix Released Bug description: ----------------------------------------------------------------------------------------- TO RE-ENABLE HIBERNATE: If the hibernate option is supported by your system and you need it, you can re-enable it as follows: https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html You may be also interested in subscribing to the bug #882040, which tracks the implementation of a configuration tool to toggle hibernate and suspend. ----------------------------------------------------------------------------------------- I'd like to propose a change in the design of Power preferences in the GNOME control center: https://wiki.ubuntu.com/Power Instead of going through the "certification" path, we can simply disable the options about suspend/hibernate if it's not supported on the current hardware (we have API for this in upower). I think this solution is more scalable, as we do not need to maintain a database with "certified" hardware. Also, we can add a button or a informative text when suspend/hibernate doesn't work to guide the users about what to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/812394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
