gnome-power-manager is just using the information that it finds out from
hal. It is actually hal that is not getting the sysfs information
properly.
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
** Changed in: hal (Ubuntu)
Importance: Undecided => Medium
Sta
Same happens on me. Notebook Vye S37B. If I issue a:
/etc/init.d/hal restart
I get the current reading but again, nothing gets updated.
/sys/devices/LNXST... shows the correct values.
/proc/acpi/... also shows the correct values.
--
gpm does not create the correct profiling files
https://bugs.lau
I think this is a bug in hal.
lshal | grep -i bat
[...]
linux.sysfs_path =
'/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/PNP0C0A:00/power_supply/BAT0'
(string)
hal reports different values than in linux.sysfs_path/* It seems that
hal reloads values *only* on an acpi
Also, notice how the Battery Charge Monitor Applet is affected by buggy
readings as well. This suggests that the bug resides in HAL!
Some more info:
[EMAIL PROTECTED]:~$ cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 4000 mAh
last full capacity: 4000 m
The correct reading, forced by triggering an event.
** Attachment added: "The correct reading"
http://launchpadlibrarian.net/12175771/Screenshot-2.png
--
gpm does not create the correct profiling files
https://bugs.launchpad.net/bugs/194052
You received this bug notification because you are a
Hello,
I have something similar on my laptop. The g-p-m shows the battery as
charging whenever I plug my wall adapter. But the battery status freezes
there after then. The attachment shows two snapshots, one of them
showing the mistaken battery reading (it shows 43% while actually the
battery was
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Confirmed
--
gpm does not create the correct profiling files
https://bugs.launchpad.net/bugs/194052
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in u
