time_critical is set to 5 minutes by default nowadays, which ought to be
enough. If you can still reproduce this in current karmic, please do so,
reboot, and then
tar czf /tmp/gpm-log.tar.gz /var/lib/DeviceKit-power
Attach /tmp/gpm-log.tar.gz then. Thanks!
** Changed in: gnome-power-manager (U
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Canonical
Desktop Team (canonical-desktop-team)
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notific
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Canonical
Foundations Team (canonical-foundations)
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notific
@DervishD: discharge-time-profile tells you the amount of time your
laptop spends with a specific battery percentage during a single
discharge. For example, in your image, your laptop would quickly
discharge from 100 to 90 percent, then slow down from 90-10, then
quickly accelerate from 10-0.
Coul
My laptop does indeed hibernate (or suspend) succesfully, but last night
I forgot to plug the AC power and let the laptop on. It didn't
hibernate.
The problem, just in case anybody is having it, is that the time
profiles are very optimistic in my machine, probably due to the fact
that I haven't le
pruch's solution (https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/135548/comments/113) worked perfectly for me in Ubuntu 8.04
(2.6.24-24-generic) on a ThinkPad X61. However, I do think this is a
bug that needs to be addressed, since the average user won't know to use
gconf-edit
Here are what seem like the relevant logs based on this document:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-7d2eb767e44a7231fae6964dcf12bc27fe507c9d
Please note that that my laptop *did* successfully hibernate, and return
from hibernation from the "gnome-power-cmd hibernate" command.
Thinkpad X32. Upgraded-from-Intrepid-to-Jaunty. Gnome Power Manager
correctly detects the battery state, correctly issues a "low battery
warning" but doesn't initiate hibernation until 0% battery is reached.
Additionally, the normal battery light starts flashing orange at the
appropriate time...b
Thinkpad T61. This worked in gutsy and hardy, but not in intrepid and
now jaunty. The fancy new status floaty warns at 4 minutes that it will
hibernate in 2. 4-5 minutes later the laptop crashes... Manual
hibernation works great.
--
[Gutsy] Action on critical battery isn't triggered - regres
this has never worked for me. Started with 8.04 LTS then upgraded to
8.10, then installed 8.10 x86_64. Lenovo Thinkpad R61. I get the
warning form gpm that my laptop will be shutdown, but it never shuts
down - just dies when power is low. If any logs are required I will
provide.
--
[Gutsy] Ac
I happened to go to a near out of battery condition on my EeePC 900 with
a recent Jaunty (as of a week ago) and the system correctly suspended to
RAM.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification becau
** Changed in: gnome-power-manager (Baltix)
Status: New => Invalid
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-powe
As there is a partial work-around I'm lowering the priority from
Critical to High. Also assigning it to the desktop team where it should
be tracked. Ted is no longer on that team.
Could some one experiencing this please give the latest status on
updated Jauntu and run 'apport-collect gnome-power-m
i solved this: i installed kde. it just works.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
d
I spoke to quickly. In fact, after having set the "pruch" configuration,
today the system automatically went into shutdown (and this is ok) but
without warning about the remaining battery charge and, moreover, it
went into halt at the battery remaining level corresponding to the first
warning.
--
The configuration of which pruch wrote solve the problem in Hardy too.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-m
** Tags added: qa-jaunty-desktop
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs ma
I'm using ubuntu 8.10 and I did this to solve the problem:
On Configuration Editor (gconf-editor)
I've set the followed keys:
/apps/gnome-power-manager/general/use_time_for_policy (false)
/apps/gnome-power-manager/thresholds/percentage_low (15)
/apps/gnome-power-manager/thresholds/percentage_crit
wow, it worked for me (still don't believe it, maybe recent updates helped)
the LCD was in "off" mode, and the Totem and Vlc were playing parallely
(well after resume I have sound problems, but that's differnent story)
(Asus laptop Z99H -- 82801G (ICH7 Family))
--
[Gutsy] Action on critical b
> gpm warned me and 1min later hibernated as set.
Well this is a problem on its own. One minute is not nearly enough.
Should we file a separate bug about this? Where is the 1 minute limit
determined?
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/
this is very bad:
i got it too!
Sony VAIO FZ31M, ubuntu intrepid
the first time, after installation it worked automatically; gpm warned me and
1min later hibernated as set.
i was so happy, the first time it ever worked out of the box.
so i never thought about it anymore.. BUT since then it neve
Yesterday the Gnome Power tool warned me that I had 1 minute remaining.
Although a 1 minute warning is useless, it at least seems to be warning
me now.
8.10 with proposed updates
Dell Inspiron 8600
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs
I can confirm the regression on my ubuntu up-to-date 8.10 64bit on a dell xps
m1330.
I can also confimrm the behaviour described by arturj in comment 104. For me as
well raising the critical action threshold to at least 360 seconds was working
as a workaround in ubuntu 8.04.
No bios updates hap
Same problem on a NEC P550. I hope changing the GConf-value helps.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manag
also still problem on Intrepid with Asus Z99H
** Also affects: gnome-power-manager (Baltix)
Importance: Undecided
Status: New
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a m
Tested in Ubuntu Intrepid - not working!
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released => In Progress
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of
Addendum: things seem to be more complicated.
Using "use_time_for_prolicy" I cannot manage to make my system shutdown
automatically, even with 360-seconds as power-off treshold. This should
work, as when my laptop battery reaches 3% the calculated remaining time
drops to 5-minutes (300sec < 360),
Using Inrepid I still have the problem on a Thinkpad T43 (g-p-m version
is 2.24.0-0ubuntu8). I think the problem is, that g-p-m recalculates
remaining time and percentage only if battery changes by 1%. Let me
explain this:
- Reading /proc/acpi/battery/BAT0/state my Thinkpad T43 battery
discharges
This bug was fixed in the package gnome-power-manager - 2.23.91-0ubuntu2
---
gnome-power-manager (2.23.91-0ubuntu2) intrepid; urgency=low
* Added two patches from Joakim Andersson <[EMAIL PROTECTED]> his
comments on the patches are below.
* Added 18_policy_actions_fallback.pat
Joakim, thank you very much for the detailed reply.
I also found out suspend after closing the lid does work after all (I
just didn't wait long enough).
I hope your patch (or maybe a more polished version) will get integrated
in the next release. Do you have a package for this, or is there an eas
Jo,
Well make it a week or two. Running the computer with the electrical
cord in place does not count (although it does add data about how the
battery charges). You can check the progress by right clicking g-p-m in
the system tray, selecting "power history" and then in that box (near
the bottom),
@joakim, so in fact I can just wait for a few days and then it should
work again? So it's then probably also better to check
use_time_for_policy again.
Or do I need your patch to get this working?
If this is true, then probably this is not a bug after all (and it
should be marked as such).
--
[
Done, will see what it does when the battery runs out again. Is this caused
by a broken ACPI as suggested by gconf-editor, or a bug in Gnome Power
Manager? Should I reset this value once the bug gets fixed?
-- Jo
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.lau
5of0,
My bet is that "use time" doesn't help, because gnome-power-manager is
coded to work just like this (I've read the code).
Like I've said in a previous comment
(https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/135548/comments/88), gnome-power-manager WILL NOT DO
ANYTHING u
Jo Vermeulen: Have you tried unchecking "use time" in gconf-editor, as
mentioned above (https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/135548/comments/19)?
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received
Forgot to mention it, but the gnome-power-cmd.sh suspend commands do
work (both for suspend and hibernate).
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I have the same problem on a HP Compaq 8510p. I found it strange that
the default settings were to "Do nothing" when battery power is
critically low, so I changed it to "Hibernate".
Unfortunately this does not work, it just keeps going until the battery
is drained.
I'm running the latest Ubuntu 8
Upstream bug report says it's solved. Why is the solution not patched in
Ubuntu?
BTW, the workaround in comment 18 works for me, on a Lenovo 3000 v100
(Ubuntu 8.04).
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug no
** Tags added: data-loss
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing li
2008/6/27 5of0 <[EMAIL PROTECTED]<[EMAIL PROTECTED]>
>:
> I'm running Hardy, upgraded via package manager, with all updates
> applied, and my computer wasn't hibernating (or notifying) on critical
> power. I unchecked the "use time" box in gconf, and it's working fine.
>
> Just FYI - it was an is
I would also note that my "time" indication never dropped below 10
minutes (I have a battery that lasts ~4.5 hours), which may explain the
lack of warning or action with the time settings.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
Yo
I'm running Hardy, upgraded via package manager, with all updates
applied, and my computer wasn't hibernating (or notifying) on critical
power. I unchecked the "use time" box in gconf, and it's working fine.
Just FYI - it was an issue on my Hardy install.
--
[Gutsy] Action on critical battery i
As I said in my last comment, I would submit my patch when I was done
with it, and here it is.
Cited from the changelog of my patched package:
* Added 11_policy_actions_fallback.patch which makes policy actions
fall back to per-percent policy if the battery profile is not good
enough
As far as I could tell from the code, Anoop P B has the correct solution
(which I can see from the output of my g-p-m).
If the battery profile of the (primary) battery isn't good enough
(accuracy less than 40%), no action will be taken, and no warnings will
be shown. This is true even if use_time_
Sorry, 20-30 minutes less time
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mail
For me, it also does not trip at 10%. It might be because it is
monitoring the time until it reaches the trip point. Highlighting the
battery shows about 20-20 minutes less time than the battery actually
has, according to the output from acpi.
--
[Gutsy] Action on critical battery isn't triggered
2008/5/26 Roberto Scelzo <[EMAIL PROTECTED]>:
> The other day I tried a debug as often suggested here and I found that g-p-m
> was configured to trigger the "critical action" when 2 minutes was left but
> g-p-m keeps on showing 5 minutes even when acpi tells that the battery
> percentage is 0%
>
The other day I tried a debug as often suggested here and I found that g-p-m
was configured to trigger the "critical action" when 2 minutes was left but
g-p-m keeps on showing 5 minutes even when acpi tells that the battery
percentage is 0%
So I adjusted the thresholds to fit what I think is cor
Things seem to fluctuate for me in Hardy. As far as I can tell, it
sometimes works and sometimes doesn't. I would love to have somebody
help us isolate the problem.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug not
Everything always worked for me (after some charge/discharge cycles
enough to create a battery profile...) but, after i've enabled laptop-
mode-tools something changed: I get some notifications about my battery
discharge but, after I get the critical warning notification the system
simply doesn't h
Shutting down on low battery hasn't ever worked for me in hardy.
This is the output of g-p-m while on batterie till the system turns of because
the batterie is completely drained.
** Attachment added: "gpm.debug.log.txt"
http://launchpadlibrarian.net/14454099/gpm.debug.log.txt
--
[Gutsy] Act
I tried it last week and it worked ok forme - wow, thanks! :)
probably the problem consists of several things, as manuel still experiences it
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you a
The problem persist in 8.04. Thins that I've notice recently
1.- gnome-power-bugreport.sh reports (AC adapter present: yes) when the ac
cable is unplugged
2.- Just few secunds before the laptop turn off the estimated remaining time
graph raise up like a "charge recovered"
** Attachment added:
To be honest this is the last time I upgrade to a new version of ubuntu as
soon as it's released. I face a lot of problems (like I did when I switched
to 'gutsy').
The worst of all problems comes to sleep/hibernate. I was satisfied with
gutsy on this (after ofcourse spending a lot of time fixing i
Everything is working now with the last version of Hardy.
nmcaramelo
On Sun, Apr 27, 2008 at 2:35 AM, Aaron Whitehouse <[EMAIL PROTECTED]>
wrote:
> Ted,
>
> I have tested each milestone of Hardy. The RC worked for me but the
> final does not. My battery is fairly old. Did anything change between
This is the log of the battery running out when I am hardly using it (to
keep the CPU at 600MHz). I still get no warnings or anything and the
machine just dies.
This makes me think that something has changed since the RC. The RC gave
me several warnings before Hibernating. I doubt that my battery
** Attachment added: "gpm.debug.log.txt"
http://launchpadlibrarian.net/13953207/gpm.debug.log.txt
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Here is a side thought that may solve this problem for some: why not
increase the frequency of battery polling as the level gets lower? There
is probably not a huge advantage in knowing each percent point change
between 90% and 80%, but it sounds as though it would make a difference
under 20%.
--
I'm currently logging all gpm output as per:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-7d2eb767e44a7231fae6964dcf12bc27fe507c9d
and running down the battery - I'll attach this when it is complete.
** Attachment added: "Output of gnome-power-bugreport.sh"
http://launchpadlibrarian.
** Attachment added: "gpm.gconf.values.txt"
http://launchpadlibrarian.net/13952834/gpm.gconf.values.txt
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Ted,
I have tested each milestone of Hardy. The RC worked for me but the
final does not. My battery is fairly old. Did anything change between
the RC and the final, or is it just a coincidence that things aren't
working for me now?
--
[Gutsy] Action on critical battery isn't triggered - regressi
this is little OT, but i must admit, that "low battery" notification
still appears, but quite early (todai it appeared at ~17% = 19 minutes),
but I hibernated yesterday with non full battery, so the numbers might
misrepresent full battery capacity)
still, where can I set the limit for "low batter
Hi Ted,
this is a serious regression!
I can confirm that in Gutsy worked. No matter if my battery is broken (30%
capacity)...I expect that g-p-m warns me and shuts my laptop down gracefully
(just like it did in gutsy).
If I can help somehow, let me know.
** Changed in: gnome-power-manager (Ubun
** Attachment added: "gpm.gconf.values.txt"
http://launchpadlibrarian.net/13154879/gpm.gconf.values.txt
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Jurgis
Could you please dump your gconf keys also:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-
3064996579b2f21cb27b49abc25849d4713e64cb
Thank you. Ted.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug
via gconf-editor
gnome-power-manager -> general -> use_time_for_policy = off
the same sad ending...
** Attachment added: "gpm.debug.log.use_time_for_policy=off.txt"
http://launchpadlibrarian.net/13154314/gpm.debug.log.use_time_for_policy%3Doff.txt
--
[Gutsy] Action on critical battery isn't
in gpm applet Preferences changed on critical to "suspend (to ram)",
as much as I remember it worked in gutsy
no luck
** Attachment added: "gpm.debug.log.GPM_oncritical=Suspend.txt"
http://launchpadlibrarian.net/13154271/gpm.debug.log.GPM_oncritical%3DSuspend.txt
--
[Gutsy] Action on criti
changed laptop-mode.conf
ENABLE_AUTO_HIBERNATION=1
HIBERNATE_COMMAND=/usr/sbin/hibernate
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=2
AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL=1
but no luck
** Attachment added:
"gpm.debug.log.GPM_oncritical=Hibernate---ENABLE_AUTO_HIBERNATION=1.txt"
http://la
with standart config
(Asus Z99H series)
** Attachment added:
"gpm.debug.log.GPM_oncritical=Hibernate---ENABLE_AUTO_HIBERNATION=0.txt"
http://launchpadlibrarian.net/13154196/gpm.debug.log.GPM_oncritical%3DHibernate---ENABLE_AUTO_HIBERNATION%3D0.txt
--
[Gutsy] Action on critical battery isn't
no luck again -- no ballon messages (they appeared at least in gutsy)
and no luck with all of the suggestions (log's will be attached)
hardy beta (upgraded as of 2007 04 06)
Gnome Power Manager 2.22.1
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/b
ok wish you luck. Mine was fixed a long time ago back in this bug. I just
set it to 2% instead of time, and it works great. My sister's windows
laptop doesn't even warn you, it will just fall asleep. My hardy warns me
several times before actually hibernating.
I don't think i will be getting a
Alright, changing threshold percent levels AND profile/time/policy did
the trick for me, so presumably the problem for me lies in the inability
to use time policy
- This DID work for me somewhere on alpha6 (see former comment by me
[2008-03-31]), and since I have values set to low=1200, crit=300,
its a good idea to buy a new battery every 18 months or so.
On Fri, Apr 4, 2008 at 7:49 PM, Ted Gould <[EMAIL PROTECTED]> wrote:
> I'm going to mark this bug as "Incomplete" right now as asac's problem
> seems to be caused by hardware (old battery).
>
> If there are other people still seeing this
I'm going to mark this bug as "Incomplete" right now as asac's problem
seems to be caused by hardware (old battery).
If there are other people still seeing this on Hardy (which has the
upstream fix) could you please post similar logs and reopen the bug.
Thank you. Ted.
** Changed in: gnome-pow
@arand
Thanks for all of the data, that helps a lot. From looking at the log
it looks like the last time that GPM gets notified of a battery level
that it's at 8 percent and that the discharge rate doesn't make it
"action level". This is likely caused by the battery being old.
What I'd recommen
I'm also attaching a summary of some of the "external" events which took
place.
** Attachment added: "gpm.debug.external.events.txt"
http://launchpadlibrarian.net/13123273/gpm.debug.external.events.txt
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.n
Oh sorry, first time I followed that link from my mail client and it
didn't jump to the right header.
Anyways, I'm attaching the full gory output of gpm-debug from 100%
charge to computer death.
Hope it says something.
** Attachment added: "gpm.debug.log.txt"
http://launchpadlibrarian.net/131
@arand
Specifically I'm looking for the events that GPM is getting and the
debug output from GPM. Under the title "Getting Info from GPM".
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#head-
7d2eb767e44a7231fae6964dcf12bc27fe507c9d
--
[Gutsy] Action on critical battery isn't triggered - r
You're right. It's still not working here on hardy.
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released => Confirmed
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a
Above suggestion (profile/time/policy) did nothing for me, I have tried
that before on this computer [Acer TravelMate 2451LCi] when I was having
the problem in Gutsy, and it didn't work then either.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs
If you have this problem, then try it with unchecking the following keys
via gconf-editor:
/apps/gnome-power-manager/general/use_profile_time
/apps/gnome-power-manager/general/use_time_for_policy
found at: http://ubuntuforums.org/showthread.php?t=487258
--
[Gutsy] Action on critical battery isn
I am not completely sure which of the debugging tasks you're after but
here goes two (which I'm not too sure how to interpret, either)...
$ dbus-monitor --session
"type='signal',interface='org.freedesktop.PowerManagement'"
- Gives me no event acknowledgements at all in the terminal, neither on AC
For those who are still getting this bug, could you please confirm that
GPM is receiving the power button event. If it is not, that is a HAL
issue. If GPM is receiving it an not acting this bug should be
reopened. To confirm whether GPM is getting the event please follow the
instructions here:
Same for me. Hardy beta 64bit on a dell xps m1330. Not working at the
moment.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-
I can also confirm that this is not working for me on the Hardy Beta,
fully updated as of now.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Latest updates for Hardy (alpha6), 3-4 days ago has broken this again
for me, no notifications, no actions on low/crit battery.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of
** Changed in: gnome-power
Status: New => Fix Released
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
Marking as fixed. With updated HAL and GPM in Hardy I am no longer
seeing this bug.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Fix Released
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bu
I'm running Gutsy Gibbon on a Toshiba Satellite M50.
I found that changing ENABLE_LAPTOP_MODE from false to true in the
/etc/default/acpi-support file fixed up the problem for me.
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You receiv
Related Bug #61201, first reported on 2006-09-18
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
I had this error on Gutsy, and in Hardy up to alpha5, on an Acer
Travelmate 2451LCi Laptop
The time_policy workaround did nothing for me.
However.
The new alpha 6 has completely solved this issue for me, I get all
notifications and computer shuts down automatically.
(Joy!)
--
[Gutsy] Action on
The same kind of errors are coming back in hardy: bug #194719 and gutsy: bug
#154003
Although they're not exactly the same they reporters are complaining about
double batteries. Could it have the same cause?
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchp
good, you always should reboot. linux will let you reboot just the relevant
portion of the system, but only if you know how. Why do you want it to
suspend on low power? It will just continue to draw power in suspend mode.
It'll then turn off without shutting down properly. I'd rather set the
li
I've written in my duplicate bug that the workaround with
use_time_for_policy did not work for me. This was only true before I had
rebooted. Now I got notification about low power, critical power and
then also a automatic suspend. Wow! :)
--
[Gutsy] Action on critical battery isn't triggered - re
It's the same bug.
This bug have's two problems related, the recognition of the battery status,
it recognizes two or more battery's when you have only one (solved with
Hardy Heron Alpha5 release), and it doesn't trigger any action when the
battery is in critical status (not solved yet).
I hope for
I have set my system to stand by if power is critical. However, it does
nothing, the battery just runs out. I have Hardy Heron, can this be the
same bug or should I look elsewhere?
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You receiv
96 matches
Mail list logo
