Comment 6 for bug 487867

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 /