Public bug reported:
My machine was suspended with a relatively empty battery. When I came
back to it in the morning it was completely dead. On inspection the
machine appears to have near exhausted its battery and woken up to allow
the OS to hibernate or similar. The machine has then re-suspended
itself, woken due to battery, re-suspended etc repeating until the
battery is dead.
My 'When power is critically low' setting is 'empty' I assume set to
Hibernate which is no longer available (this is an upgrade). And the
machine is set to suspend on lid close. I am therefore conjecturing the
machine is woken by the low power state, has no valid action on power
low, has a closed lid so it implements that. This leads to the loop.
We likely should be upgrading peoples settings if they have 'Hibernate'
set to be poweroff or whatever the approved solution is.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Wed May 2 09:45:18 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to precise on 2012-01-04 (118 days ago)
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/993126
Title:
on battery low the machine got into a suspend/resume cycle until the
battery was flat
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/993126/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
