*** This bug is a duplicate of bug 531190 ***
https://bugs.launchpad.net/bugs/531190
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 531190, so it is being marked as such. Please look
MSI wind u200, Ubuntu 10.04. Bug still exists. Battery power applet and
acpi -b works cprrect though.
To stop warning every time you pull the plug, repeat next steps:
Run gconf-editor.
Navigate to Apps / gnome-power-manager / notify.
De-select the option discharging.
No need to restart, just
When fully charged and after I pull out the power cable, Ubuntu claims
the power is critically low and starts to hibernate. Before going into
hibernation I did see a message claiming I had 55 minutes left of
battery power. Laptop is: LG G51-NPR031-xxx. Celeron Processor.
--
Power manager
The popup warning message claims I only have 2 minutes left, but when I
press the battery power applet, it says 55 minutes.
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug
Same here, msi wind u100. For some reason I only receive the warning but
no action is taken. After a while the estimated remaining battery time
is correct, so the only problem I have is a warning every time I pull
the plug.
--
Power manager mistakenly thinks my battery power is critically low,
Dell Vostro 1510, Same simptons
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This affects me too, on an MSI X340. Under both Karmic and Lucid,
immediately after pulling the plug, it would tell me I only have 2
minutes of battery power remaining. Under Karmic, it was merely
annoying...
Under Lucid, it pops up a dialogue box telling me the system is
critically low on
Alfrenovsky
I have not been able to get your script to work [yet] for me but I
confirm I can see anomalous readings after both plugging in and removing
the power adapter on the output from upower -dump on the MSI Wind.
If this is a common BIOS problem why have we not seen it before. I have
been
I have just checked the setup in Jaunty and I find that there are more
options under gconf-editor - apps - general including a key called
invalid_timeout which does exactly what we need - the description is
The invalid timeout is in ms for Power actions. Set longer if you get
a 'battery critical'
Peter:
Forget my script. I didn't know that upower -d gives you the same
information. cooked.
I had the same strange remaining times with karmic just after
plug/unplug, I didn't report it as a bug before cause I had my
hibernation support broken I disable it and I didn't notice the problem.
I
Alfrenovsky
The 'drain in 10 minutes' limit might still gives us a potential problem
between 10 minutes battery life left and the 2 minutes that is the
normal shutdown point on machines that have intermediate readings.
A delay of 30 secs would use some of the hibernate time and need the
Peter.
I'm not talking about 10 minutes of remaining time (current capacity / current
rate).
What I said is that when (design capacity / current rate) = 10 minutes We
should ignore the data because the current rate should be fake.
design capacity is the design battery full charge (usually a
I have a zareason computer which is MSI underneath. I worked around the
problem by unsetting /apps/gnome-power-
manager/general/use_time_for_policy in gconf-editor
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
I can confirm I am also seeing the problem on an MSI Wind U100 (with
original bios) and had found the fix using setting 'use_time_for_policy'
to FALSE works. The problem occurs with two different batteries.
Looking at the various charts one can view using the gnome-power-manager
gui there seems
In Dell mini 10 there are anomalous readings just after plugging or
unplugging.
The problem is the BIOS. gnome-power-manager is working fine.
Using change instead time to take actions is not a fix, is a workaround.
Another workaround will be IGNORING absolutelly the acpi battery informatión
when
Great. Another MSI Wind specific bug. I have a Medion Akoya which is the
same thing as MSI Wind and I have this issue too.
The workaround in Comment #11 regarding setting 'use_time_for_policy' to
FALSE works. (Thanks)
--
Power manager mistakenly thinks my battery power is critically low, and
Same thing for me with a Dell inspiron 1010 (aka mini 10)
In my case the problem is the netbook, not gnome-power-manager.
But because its a common problem. gnome-power-manager seems to be the right
place to put a workaround.
If I watch /proc/acpi/battery/BAT1/state I can see that inmediatly
I tried this again with gdm stopped, so changes can happen with no
suspending or hibernate.
As you can see here in my battery watch file this time my BIOS took 15
seconds to start giving reasonable values.
My netbook charges at about 35-40 Watts, discharges at 13 Watts. 700 to
750 Watts is more
My post #12 was bas, there was really 72 mW and no 72000.
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This procedure fixed it for me (Advent 4211 which is a wind clone):
Press Ctrl-Alt-F2 and use the pop-up to launch gconf-editor.
Navigate to Apps / gnome-power-manager / general.
De-select the option use_time_for_policy.
No need to restart, just close the config editor.
I read in another forum
I'm also affected by this on an MSI Wind U135.
Here's the result of upower --dump after killing gnome-power-manager:
Device: /org/freedesktop/UPower/devices/line_power_ADP2
native-path:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C09:00/ACPI0003:00/power_supply/ADP1
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
** Attachment added: upower-output
http://launchpadlibrarian.net/45755527/upower-output
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member
Same insue here on Ahtec NetBook LUG(MSI wind clone)
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for your bug report. Please stop gnome-power-manager (killall
gnome-power-manager), unplug the power cord and then post the output of
upower --dump
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
Power manager mistakenly thinks my battery power is
Here is my plugged and unplugged dump!
** Attachment added: a/c plugged
http://launchpadlibrarian.net/45596430/upower.dump
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug
** Attachment added: unplugged
http://launchpadlibrarian.net/45596469/upower_unpluged.dump
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a
** Also affects: gnome-power
Importance: Undecided
Status: New
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same problem on a MSI Wind u100x with ubuntu 10.04
-I can boot the pc with the sector adaptater pluged-in, but when I unplug it,
no matter what the current level of charge of the battery is, the system
hibernate. (just like Jonathan)
-An important precision: If I boot the computer
The same like in my case with LG X110
See bug # 516023
--
Power manager mistakenly thinks my battery power is critically low, and
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have exactly the same issue on my MSI Wind U-100.
Even in 9.10 I had that incorrect notification of 2 minutes remaining, just in
that version the auto hibernate option was disabled i guess.
for a temporary solution i set the behaviour for critical battery to suspend,
so the computer can be
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43457041/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43457042/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43457043/Dependencies.txt
**
32 matches
Mail list logo
