[Bug 861976] New: "When battery power is critical" in gnome-control-center, "Power" does not allow changes
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c0 Summary: "When battery power is critical" in gnome-control-center, "Power" does not allow changes Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: gp@suse.com QAContact: qa-bugs@suse.de CC: fcrozat@suse.com Found By: --- Blocker: --- Created an attachment (id=577012) --> (http://bugzilla.novell.com/attachment.cgi?id=577012) Screenshot Unlike "Automatic suspend", the field "When battery power is critical" does not allow changing its value but is hard coded to "Power Off". This is a regression from earlier versions. I do want to make that "Suspend to Disk"/"Hibernate", and the GUI should offer this configuration. See the attached screenshot. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c1 --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2014-02-04 09:50:00 UTC --- 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.. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c2 --- Comment #2 from Atri Bhattacharya <badshah400@gmail.com> 2014-02-04 09:56:16 UTC --- Created an attachment (id=577057) --> (http://bugzilla.novell.com/attachment.cgi?id=577057) System settings -> Power Even stranger: on my laptop, the Power modules in system settings has this working just as I expect it to, with hibernate selected by default for when "Battery is critical" and the option to choose "Power off" available from the menu. See attached screenshot. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c3 --- Comment #3 from Gerald Pfeifer <gp@suse.com> 2014-02-04 14:22:06 CET --- (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. 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? -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c5 --- Comment #5 from Gerald Pfeifer <gp@suse.com> 2014-02-16 23:39:34 CET --- Thanks for digging into this, Fred!
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)
YES, absolutely please. My primary challenge and frustration as a user was that it just seemed not to work without any indication on why (not). So, regardless of anything else, if we do not support something which generally works, explain, even if briefly.
- 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)
My preference would be to still allowing me to set the configuration to hibernate, even if currently not possible, and then fall back as you indicate. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c6 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dliang@suse.com --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2014-02-17 09:36:36 UTC --- David, could you have a look at it ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |882799 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=861976 https://bugzilla.novell.com/show_bug.cgi?id=861976#c7 Michael Catanzaro <mcatanzaro@gnome.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcatanzaro@gnome.org --- Comment #7 from Michael Catanzaro <mcatanzaro@gnome.org> 2014-07-02 02:52:52 UTC --- Has this been reported upstream? -- 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.
participants (1)
-
bugzilla_noreply＠novell.com