https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c4 --- Comment #4 from Frederic Crozat <fcrozat@suse.com> 2014-02-04 13:32:18 UTC --- (In reply to comment #3)
(In reply to comment #1)
Strange, I see the same issue but the default is "hibernate" in dconf ( gsettings get org.gnome.settings-daemon.plugins.power critical-battery-action).
I wonder if the call to logind "CanHibernate" is failing, causing "hibernate" default not be available..
What does "upower --dump" give?
Based on your response, I had a look and indeed at first I had
Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no
Then I restarted a program consuming some memory, can-hibernate went to yes, and now my screenshot looks exactly like Atri's.
Hmm, I also have can-hibernate as "no"
In a way this is solved.
Though in a way it is not. If this is confusing to you and me, I bet the user experience is even more confusing to a more naive user.
What can we do here?
I've checked systemd code and it only allows hibernation if memory used (Active in /proc/meminfo) is below 98% of the swap partition size. I'm not sure how to improve this, some possible solutions: - specify in the configure UI that current memory usage is higher than swap size, not allowing hibernation (although user won't really be able to change that) - still allow hibernation but when it is done as "critical" and if conditions aren't met anymore, push some warning and after some delay, shutdown the system (not great) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.