@Marco - > power-management in openSUSE 13.1 is really inefficient and unreliable.
I read your email, but I never responded to it as I have personal experience with over half a dozen laptops which behave differently (in fact, exactly as you request). For example, on the x220 I'm using to write this email, Battery Notification is working, Suspend to RAM at battery threshold is working, as is Hibernate. Indeed, Gerald's issue is a case of the behavior you complain about in your personal email working..just working a little too viciously. Rather than making sweeping statements that I have to try hard not to take personally, could you please file a bug report with details such as extracts from /var/log/messages and/or GNOME Settings Daemon logs (produced by running "gnome-settings-daemon --no-daemon --debug &> g-s-d-debug.txt") that show what's going on when power is low..we might actually be able to help :) On 30 May 2014 07:48, Gerald Pfeifer <[email protected]> wrote: >> - How can we get this fixed properly such that whatever is deciding >> my battery is running low actually uses the same source of information >> as the status indicator (which gets it right)? GNOME relies heavily on upower, and I suspect the problem lies either between upower, or in gnome-settings-daemons interpretation/logic/implementation of what information it's receiving from upower. There is evidence of upower struggling with multiple batteries for a very long time (eg. https://bugzilla.gnome.org/show_bug.cgi?id=570133 ) I cant reproduce this problem on my hardware (I only have a single battery), but GNOME:STABLE:3.12 contains both a new gnome-settings-daemon and a new upower (it was mandatory for GNOME 3.12). If you're willing to go for a 'shot in the dark', you might have luck adding the following repository and running zypper dup (of course, I'd recommend backups/snapshots, etc, just in case it doesn't work) http://download.opensuse.org/repositories/GNOME:/STABLE:/3.12/openSUSE_13.1/ >> - As a stop gap measure, but generally: How can I avoid such a forced >> shutdown? Frankly, I'd rather let the system run out of battery than >> anything being force on my. > > ...any takers on this aspect? > > I just lost work with only one battery in the system. When I got > the critical power warning, I suspended to RAM, reconnected power, > loaded for an hour and resumed, and then the system still decided > to shut down. :-( Is there a reason the system can't hibernate? the default behavior for critical battery power shortage is hibernate, which, while imperfect especially in your case, should at least result in work being maintained. > Since GNOME in openSUSE 13.1 is actively hurting me in the context > of powersaving, I'd like disable this "shutdown when GNOME feels > the battery is nearly empty" functionality. > > > 1) In the system configuration I see "When battery power is critical" > under "Power", alas that only offers "Shutdown" and "Hibernate". > > 2) In dconf-editor I found critical-batter-action which seems to do > what I need, alas trying to set it via the command-line fails: > > dconf write > /org/gnome/settings-daemon/plugins/power/critical-battery-action nothing > > just gives me "error: 0-7:unable to infer type". > > How can I set this programmatically? > Try, gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action 'nothing' This appears to set things the way you want in dconf-editor - unfortunately my laptop has too long a battery life for me to confirm it works for some hours yet :) Hope this helps, - Richard -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
