Hi,
I just installed Ubuntu 11.10 and the issue occurred to me. I was on
battery power and suddenly a pop up came up saying laptop battery
critically low and need to suspend. After I clicked ok the laptop
suspended. Though the battery capacity was 70% at that time. My laptop
is Compaq Presario
The work around I tried is mentioned in
Bug #531190
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/473552
Title:
Battery incorrectly reported as critcally low at when almost full
To manage
I'm also having this problem, and by this date it has not been fixed
yet!.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/473552
Title:
Battery incorrectly reported as critcally low at when almost
I'm having the same issue with my Aspire One and the Lucid RC. It
wouldn't be a problem except that when the power manager reports the
wrong percentage of power (believing that my battery can hold 270 watts
of power when it only holds about 48) the computer automatically shuts
down (that's the
I've now moved to Fedora 12 and the install has revealed the cause of my
fan control problem. The fan running constantly and possibly the high
temperature value is down the the acer aspire one BIOS upgrade which
breaks all third party fan control apps including in windows.
As for the original
OK, I've linked to your comment in bug #421985 regarding the patch
feedback. If you could monitor that issue and report any further
requested information that would be great.
The patched kernel is actually rather old so it's possible it reverted
some fixes that had been in the unpatched one you
Hello David
Sorry I should have been a bit clearer.
When I posted the last comment I'd installed the patch and rebooted and waited
for the battery to charge the last 10 percent or so.
It was still showing a charge rate of 720.0 odd watts.
After the patch install and reboot with the charger
Think I just noticed another bug since i applied that patch. I didnt
notice earlier because I had headphones on listening to music but my fan
is running constantly even with acerfand installed. it doesn't feel hot
at all but the the temperature reading is as follows
bsheph...@bs-netbook:~$ cat
Hello David
I decided to bite the bullet and upgrade my aspire one to 9:10 so that I
can do as much testing as possible on this. I upgraded and let it
charge, run flat, and charge again with no patch applied. I kept the
power history graph open so I could watch for any blips and at about 90%
on
Unplugged power but power applet still remained in the charging state.
rebooted the machine and now this has corrected it's self. currently all
the battery stats look normal but I'll give it a few charge cycles and
report any other occourances.
--
Battery incorrectly reported as critcally low at
Hi Ben,
Cool, thanks for all your help!
Just to make sure I understand you correctly, the weird reporting in
charging/discharging went away after you rebooted once, right? It's not
a recurring problem?
So the patch seems to fix the issue without creating any more?
Thanks again,
David
--
Hi Ben, thanks for your patience. Unfortunately, I can't get Lucid Alpha
3 working on my laptop at all right now because of another bug so I
can't help you much with the upower stuff. As far as I can tell, apport
won't actually give very good information in Lucid anyway because they
haven't added
Hello David / Konstantin
i've downloaded Lucid Alpha 3 but unfortunatly I wasn't about to get any
information what so ever out of upower --monitor-detail as even when
unplugging and plugging back in it returned no output what so ever. Also
the battery charge applet didn't give any options when
Ok apport-collect doesn't work in lucid because devkit-power is not
installed although from what I've read it is but has just been renamed
upower. Would I need to create another bug for that? I'm pretty new to
Launchpad and I've not quiet got my head around all this yet.
From what I can see it
Hi Ben,
No, I'm not sure. In my issue upower send wrong data just when unplugg
or plug power cord.
Maybe it is not upower issue, something wrong with hardware or it is
some transient process.
But gnome-power-manager reacts to this transient process with message
and hibernating.
BTW. yesterday
Hi Konstantin, thanks for the information. Are you sure your issue is
actually the same as Ben's? He never said anything about the problem
only being immediately after unplugging.
Can you confirm that the issues are different, Ben?
--
Battery incorrectly reported as critcally low at when almost
AC cable was unplugged then after about 5 sec. plugged back then Ctrl-C
to prevent susbend
** Attachment added: gpm.debug.log.txt
http://launchpadlibrarian.net/40045255/gpm.debug.log.txt
--
Battery incorrectly reported as critcally low at when almost full
I file new bug
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190 because
apport-collect is rejecting to post here:
Package devicekit-power not installed and no hook available, ignoring
--
Battery incorrectly reported as critcally low at when almost full
Great, thanks for the reply. I'm going to confirm this bug since you've
provided more than enough information to confirm that it is, in fact, a
bug.
If you can test further with Lucid Alpha 3 (released Feb 25) that would
be most helpful. If the bug is still present then we'll just have to
hope a
Actually, on second thought, if you can confirm that this is still
broken in Lucid Alpha 3 (please provide devkit-power output), I'll
create an upstream bug report for this.
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received
I can confirm my case
(https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/516023 ) in
Lucid Alpha 3.
My case is: When AC is unplug I immediately see battery critically low
then the hibernate/suspend action is happend according the settings in
power management.
The same
Hello David
Yes it seems like devkit-power reporting bad data is what's at fault. I
didn't check the AC when unplugged because when I managed to rebuild the
machine with the parts that eventually arrived I built it with 9.04
because 9.10 was unusable. I ran the above with live 9.10 so with no
Hi Ben,
Thanks for the update. Just to clarify, the root problem seems to be
that devkit-power is reporting erroneous data, causing these low battery
warnings and forced shutdowns?
It also still does not detect when you unplug the AC?
Thanks.
--
Battery incorrectly reported as critcally low
Could it be that https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/516023 is dublicate of this one?
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received this bug notification because you are a member of Ubuntu
I am also using an Acer Aspire One A110 and Ubuntu 9.10 and I am having
the same problem. However, I don't think it is a problem with Ubuntu
because this problem was present on my Windows XP installation, too,
before I installed Ubuntu. Unless XP and Ubuntu share some apparent
flaw? Could this
Oddly, I've been having this issue since November as well.
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
manifestkni...@gmail.com
Subject: [Bug 473552] Re: Battery incorrectly reported as critcally low at when
almost full
To: frank.jam...@btinternet.com
Date: Friday, 22 January, 2010, 18:20
Oddly, I've been having this issue since November as well.
--
Battery incorrectly reported as critcally low
Hello David
I'll do this as soon as I can but my aspire one is currently out of
action and awaiting parts which seem to be on a slow boat from China. As
soon as i get it back up and running again I'll sort this out.
Kind Regards
Ben
--
Battery incorrectly reported as critcally low at when
Re-assigning to devicekit-power since it's reporting bad data and g-p-m
is just copying it.
** Package changed: gnome-power-manager (Ubuntu) = devicekit-power
(Ubuntu)
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received this
Invalidating upstream task, at least until we can confirm that it's not
an Ubuntu-specific bug.
** Changed in: devicekit-power
Status: New = Invalid
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received this bug
Actually, could you please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 473552
This will help us to find and resolve the problem. Bear in mind that you
may need to install the python-launchpadlib package from the universe
** Also affects: devicekit-power
Importance: Undecided
Status: New
--
Battery incorrectly reported as critcally low at when almost full
https://bugs.launchpad.net/bugs/473552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug seems to be related to other simalar issues such as Bug #393008
I notice that the power manager applet doesnt recognise the AC has been
unplugged. After running like that for an hour or so shut the machine down.
Restarted later in the day and the indicator now correctly reported
33 matches
Mail list logo
