*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
Confirmed on HP Pavilion, with Mint Lisa 12
it is not displaying any message , and takes no action on critical
battery action, whether use-time-for-policy is true or false (i.e.
whether using percentage or
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
Action on critical battery isn't triggered
* You can subscribe to bug 135548 by following this link:
Also confirmed on the MacBookPro - 2.1
I really don't see how this can claim to be a production ready OS if it
can't at least tell me my battery is about to die. I don't usually run
it with a battery, but that's to save my battery. However, this bug
makes me very reluctant to use my laptop as a
Confirming the problem on a Thinkpad T61.
--
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/481576
Title:
Action on critical battery is not triggered -
Sorry, I should have liked to add: I didn't even receive the critical
warning, altough power history shows that critical threshold was passed
7 minutes before the laptop switched off.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
wanted to add that i am running 10.04 now, and the problem is still
there. if i unplug the notebook from AC, and battery level is at 197mAh
(according to /proc/acpi/battery/BAT1/state), no message is displayed.
according to /proc/acpi/battery/BAT1/info low battery warning should
happen at 300mAh,
confirmed on a Thinkpad X32 and a Samsung N150, both with Ubuntu 10.04.
--
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/481576
Title:
Action on critical battery is not
Im running Lucid Lynx (i386) on a Acer Aspire One D150, (upgraded to 2gb
RAM) i can confirm that hibernate function works for me if I have the
value percentage_action on 5 or higher, then the system hibernates
automatically.
I also tried lower values than 5 and then nothing happened until battery
I'm curious to know where gnome-power-manager gets the battery info and
state information. If it's getting battery information from
/proc/acpi/battery/BAT*/info, we can call this $info, then why does it need
a percentage? the info file has the mAh when the battery is low and when it
is critical.
Some additional information to my last post:
I figured out that the solution suggest by Maciej Strzelecki, setting
use_time_for_policy to false, worked in my case (HP dv3550eg, ubuntu
10.04 64-bit).
!! It is important that you either restart the system or kill gnome-
power-manager and start it
I am running 10.04 32bit and this bug definitely affects me as well.
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
9.10 amd64 (Dell XPS 1645 laptop) and I get that as well.
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
Confirmed for lucid on HP Pavilion dv3550eg.
On previous installation (ubuntu 8.10) at least acoustic warning at low
battery worked. I don't remember if it hibernated.
I'd also vote for I higher priority.
--
Action on critical battery is not triggered - gnome-power-manager
I can confirm this bug on a
- Toshiba Satellite L300 26K
- with ubuntu 9.10 all updates applied
Percentage is displayed correctly(+ remaining time),
I tried:
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug
accidentally hit hotkey for post...
anyways, i tried:
- changing the gconf values to percentage
- altering percentages
still, I never get a notification or a sound if percentage
is at LOW/CRITICAL/ACTION, and at 0% the notebook just dies, no shutdown no
nothing.
May I ask why the priority of
This bug also exist in lucid. I attached gpm.log from acer aspire one
d250. On last minutes battery is at 3% and suddenly stays at 0%.
Discharging to 0% can damage battery!
** Attachment added: gpm.log
http://launchpadlibrarian.net/49825127/gpm.log
--
Action on critical battery is not
My hardware is Lenovo s10-2, about 2 months old, battery in mint
condition, Ubuntu 9.10 with latest updates applied.
Experience: I kept a close watch on Power Statistics - Detail. My
remaining time, percentage etc displayed correctly all the time. When
percentage and remaining time reached 0, the
update: out of curiosity, set threshold levels of _critical and _action
to 93 and 92 percent respectively. (battery fully charged)
Killed and started gnome-power-manager --no-daemon --verbose and waited.
I when reached 92%, another minute passed, when I received a warning
that it is going to
Kevin wrote above about loss of Li-Ion capacity by draining it. I took
my (rather new) battery back for warrantee since capacity was so low.
What I found is a problem in battery management on the laptop/software.
My battery powers the unit for 25-30 minutes. I believe that failure to
hibernate
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I'm running Karmic, and am still experiencing this bug. I'll try
bumping the time_action and time_critical values to more conservative
settings, and will post an update soon. As I have an old battery, my
Thinkpad's critical power level is around 5%. Hibernate should occur at
4%, or 3% at the
P.S. When running gnome-power-manager in verbose mode, I get no output
before hibernate doesn't occur and the system dies. I mounted my
partition -o sync, and tail -f gpm.log in another tab, just to make sure
I wouldn't miss anything.
--
Action on critical battery is not triggered -
I'm fairly certain that I've experienced this problem since Gutsy. I'm
running Jaunty now and still have the problem. Incidentally, this bug
should be considered critical. Apparently, draining a Li-on battery
completely kills the battery (mine only has 9.8% of it's original
capacity).
I've
Changing percentage_action to 3 or greater and use_time_for_policy to
false is a temporary solution for this bug.
gconftool-2 --type int --set
/apps/gnome-power-manager/thresholds/percentage_action 3
gconftool-2 --type bool --set
/apps/gnome-power-manager/general/use_time_for_policy false
In
In the first minutes before the end of the battery, charge is over 2%,
and then suddenly 0% what g-p-m is probably getting lost by. In gpm.log:
- percentage zero, something's gone wrong.
** Attachment added: gpm.log
http://launchpadlibrarian.net/35748574/gpm.log
--
Action on critical battery
I can confirm Maciej's observation. After a short period of time on
critical power it drops to 0%.
I also wonder if it could be something about the missing time left which
g-p-m never shows on my laptop. Settings and thresholds for g-p-m in
gconf-editor indicate that g-p-m is working based on
** Attachment added: gconf-editor settings for g-p-m (thresholds)
http://launchpadlibrarian.net/35754201/Screenshot-Configuration%20Editor%20-%20thresholds.png
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug
In the previous bug report I wrote about the same problem. From what I
noticed, nameiner also has the HP laptop (information about the
battery), it can be a clue. My model is HP 6530b.
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You
I did as you told me:
killall -9 gnome-power-manager
gnome-power-manager --no-daemon --verbose ~/gpm.log 21
This created an empty log file.
I let it run on battery until 2-3 minutes after the critical battery warning
was shown.
--
Action on critical battery is not triggered -
Hm, it shouldn't be empty any more after some seconds.. Is it still?
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I had it running for over an hour before my battery was drained. The file was
still empty.
When I run
gnome-power-manager --verbose ~/gpm.log 21
it fills up pretty fast. I added that log yesterday already (see post
#2).
--
Action on critical battery is not triggered - gnome-power-manager
Ah, sorry; thanks!
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35590170/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/35590171/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/35590172/GConfNonDefault.txt
** Attachment added: output of gnome-power-manager --verbose
http://launchpadlibrarian.net/35591704/gpm.log
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Can you please open a Terminal, do
killall -9 gnome-power-manager
gnome-power-manager --no-daemon --verbose ~/gpm.log 21
then let the battery time out (or at least go to something like 1%).
After that, please attach gpm.log here. Thanks!
** Changed in: gnome-power-manager (Ubuntu)
35 matches
Mail list logo
