2015-09-04 09:30:07 |
cl-netbox |
bug |
|
|
added bug |
2015-09-04 09:33:30 |
cl-netbox |
tags |
|
management power |
|
2015-09-04 09:36:14 |
cl-netbox |
description |
When the battery is discharged completely, notebooks hibernate instead of shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs to 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
When the battery is discharged completely, notebooks hibernate instead of shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
|
2015-09-04 09:43:34 |
cl-netbox |
tags |
management power |
battery management power |
|
2015-09-04 12:24:13 |
Ubuntu Foundations Team Bug Bot |
tags |
battery management power |
battery bot-comment management power |
|
2015-09-04 12:42:17 |
cl-netbox |
affects |
ubuntu |
d-conf (Ubuntu) |
|
2015-09-04 12:43:28 |
cl-netbox |
tags |
battery bot-comment management power |
battery management power |
|
2015-09-05 09:06:28 |
cl-netbox |
description |
When the battery is discharged completely, notebooks hibernate instead of shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
After discharging the battery completely the notebook suspends instead shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
|
2015-09-05 09:07:18 |
cl-netbox |
description |
After discharging the battery completely the notebook suspends instead shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
After discharging the battery completely, the notebook suspends instead shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
|
2015-09-05 09:28:15 |
cl-netbox |
description |
After discharging the battery completely, the notebook suspends instead shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
After discharging the battery completely, my notebook suspends instead of shutting down.
To prevent the battery from getting damaged, it is important that the machine shuts down.
This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10.
In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'.
In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'.
In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again.
So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely!
This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action.
It leads to unwanted behavior of machines when users change power settings by executing:
"gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" |
|
2015-09-08 14:57:02 |
Launchpad Janitor |
d-conf (Ubuntu): status |
New |
Confirmed |
|
2016-02-10 11:07:43 |
Vishwa Prakash H V |
d-conf (Ubuntu): assignee |
|
Severus Tux (severustux) |
|
2016-02-10 11:07:49 |
Vishwa Prakash H V |
d-conf (Ubuntu): assignee |
Severus Tux (severustux) |
|
|
2016-03-09 06:35:07 |
SV |
bug |
|
|
added subscriber DoDuS |
2017-02-14 04:35:24 |
Adolfo Jayme Barrientos |
d-conf (Ubuntu): importance |
Undecided |
Medium |
|
2019-10-08 04:45:55 |
Subham Satyajeet |
bug |
|
|
added subscriber Subham Satyajeet |