----- Original Message ----- > Hi, > > On Thu, 2018-09-13 at 10:40 -0400, Bastien Nocera wrote: > > Adding a new configuration option doesn't explain to the end-user why > > this might be a bad option to enable in the current state. It doesn't > > explain > > why it's not enabled by default if it's a good feature to use. > > We already have the "Hibernate" option in gnome-control-center. And, to > be honest, the main issue with enabling SuspendThenHibernate is > hibernation itself not working in the first place. But why don't we disable those at the systemd level then? If we know they're broken, they will be broken for every use case. Disable it in systemd in Fedora, the "Can*" functions in systemd return false, and the options don't appear in GNOME. > So, I don't really see that we would be adding a lot of extra confusion > to the control-panel. It would get added to the configuration panel, and be selectable, and be broken. It doesn't make anything better, it just shifts the blame to the user who's supposed to know that hibernate is broken. _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@xxxxxxxxxxxxxxxxxxxxxxx
