----- Original Message ----- > > On Wed, Sep 12, 2018 at 8:00 AM, Bastien Nocera <bnocera@xxxxxxxxxx> > wrote: > > https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/a6e3ee40d90294c603e1108e19ef8fe8e6af61eb > > Bastien, > > It seems (a) more work is required in systemd, and (b) even if that > work were completed, it's still unsupported and expected to fail at the > kernel level. > > Will you reconsider the upstream behavior? I'm not the upstream (or downstream) maintainer, I wasn't the author, or the committer but if it doesn't work in systemd, then it simply needs to disable that feature, the code will happily not use the feature if the "CanSuspendThenHibernate" call fails. It shouldn't require any changes in GNOME. I should also note that I'm really not interested in discussing power management with Fedora anymore, the decision last cycle to disable automatic suspend was the last straw. Fedora didn't put any pressure on mutter maintainers to have the fix necessary for the feature to work as expected, I had to write the mutter patches myself upstream, which weren't picked up by Fedora and waited until a .1 upstream release to be merged. The patches were working and available before you chose to revert the behaviour in Fedora, despite me repeatedly saying that the problem should be fixed in mutter, and with no clear forward path as to when that change in configuration compared to upstream would be removed. It's still there in the F29 betas: https://src.fedoraproject.org/cgit/rpms/gnome-settings-daemon.git/tree/org.gnome.settings-daemon.plugins.power.gschema.override _______________________________________________ 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
