I found the workaround. Critical battery trigger has two modes:
'nothing' will ignore a seemingly critically low battery signal
'suspend' is the default which causes the computer to suspend upon receiving
this erroneous signal
Check the current mode:
$ gsettings get org.gnome.settings-daemon.plugins.power critical-battery-action
Change the mode to do nothing
$ sudo -s
# cat >
/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.override
<< HERE
[org.gnome.settings-daemon.plugins.power]
critical-battery-action='nothing'
HERE
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
$ sudo dconf update
$ rm -r ~/.config/dconf/user
$ gsettings reset-recursively <schema>
$ gconftool-2 --recursive-unset /
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-power-manager (Ubuntu)
Assignee: (unassigned) => David Bensimon (davidbensimon)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/487867
Title:
No preference to enable/disable low battery alarm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/487867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
