On 30 July 2014 21:10, Gerald Pfeifer <[email protected]> wrote:
> I am running this now and am pleased about the improvements I am
> seeing.  Nothing revolutionary, but network management for wired
> connections seems improved, some visual improvements (somewhat
> approaching Android in terms of messages boxes, interestingly),
> a detail here, a detail there.

I just got back from GUADEC, I'm expecting us to see more tweaks and
tunings in 3.14 and 3.16 in this area..they're still not happy with
how notification works, though they seem pleased with the general
direction of travel

> However, I have not been able to run down batteries with two batteries
> installed to see whether upower/GNOME now cooperate more nicely, but
> may get a chance next week.

Please let us know how it goes

>> 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.
>
> Firefox consumes so much (virtual) memory that my 2GB swap partition
> that I've had for a couple of years is not sufficient any more, now
> that my notebook features 8GB of RAM.  With the right swap/suspend
> strategy that should be easily sufficient (I do not have > 2GB of
> dirty pages), but that's not a GNOME problem.

No, but the 'fix' is already in Factory (and I think it might have
even shipped in 13.1) - YaST has a tickbox in the partitioner during
installation to 'Expand Swap for Hibernate'

That's no good for those of us who have it too small and who
upgrade..but I guess you could get creative with shrinking partitions
and creating a second swap partition to make up the difference

> Noooow, a curious question:  If, after the change above, I run
>
>   gsettings get org.gnome.settings-daemon.plugins.power 
> critical-battery-action
>
> that shows 'nothing' as expected.  In the graphical settings, the
> Power module shows "When battery power is critical" "Power off",
> however.
>
> Bug or "feature"?

I imagine "feature" - Settings modules can only show settings it's
aware of (even if theres 'hidden' values in gsettings).. I did speak
to somebody at GUADEC however who understood the problems this causes,
I'm hoping we see changes in upcoming versions.
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to