Bug 100629

Hm, according to some upstream bugs, klaptomdaemon does support ACPI (see, for
example, http://bugs.kde.org/show_bug.cgi?id=48983; and
http://bugs.kde.org/show_bug.cgi?id=37905 explicitly says "2002-08-31 10:58 ...
current klaptopdaemon HEAD code already has this feature" and "2002-10-03 20:00
... This was fixed a while back in CVS it will be included in 3.1.")

So, why isn't it working in beta1 (klaptopdaemon simply draws an X'ed battery
icon and claims the machine does not have APM)?

It works for me (ever since 9). Did you load the ac/battery modules?
What does /proc/acpi/battery say?

yes, for working the ac/battery modules should be loaded before. Does it work
for you?

Ah, yes - I believe I loaded the modules _after_ I started the KDE session. So,
I guess, the only bug here is that it only checks at startup and does not notice
if modules are loaded afterwards. 

Except that now it says that my battery is 152% charged...

strange, the percentage is correctly showed for me. What for battery time do you
have by 152% charged?

Please check the content of /proc/acpi/battery to see if this is a kde
parsing bug or an acpi bug.

It works fine here, even with two batteries in the laptop.

Sorry, it does not work with two batteries (it did with shrike). I get 163%
as well.

I did not have a chance to do much tesing yet, but I get 152% (and no time
reported) with just one battery. But that is only on AC - when running on
battery power, the percentages and the time appear correct.

With one battery everything is fine for me. With two batteries it seems
to forget to divide by two (it displays 170% when BAT1 is 70% and BAT2 100%
charged). AC or not makes no difference. 

If you compare "remaining capacity" from /proc/acpi/battery/Bat1/state
with "design capacity" from /proc/acpi/battery/Bat1/info, does acpi
give correct values?

Interesting, for some reason when AC is plugged in, the design capasity is
reported instead of the actual one:

On AC:

% cat /proc/acpi/battery/BAT0/state
present:                 yes
capacity state:          ok
charging state:          unknown
present rate:            unknown
remaining capacity:      66000 mWh
present voltage:         16519 mV

% cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         66000 mWh
last full capacity:      43580 mWh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 3000 mWh
design capacity low:     1000 mWh
capacity granularity 1:  200 mWh
capacity granularity 2:  200 mWh
model number:            0004M778
serial number:           1403
battery type:            LION
OEM info:                SANYO

Right after AC is unplugged:

% cat /proc/acpi/battery/BAT0/state
present:                 yes
capacity state:          ok
charging state:          discharging
present rate:            24629 mW
remaining capacity:      41620 mWh
present voltage:         16519 mV

% cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         66000 mWh
last full capacity:      43580 mWh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 3000 mWh
design capacity low:     1000 mWh
capacity granularity 1:  200 mWh
capacity granularity 2:  200 mWh
model number:            0004M778
serial number:           1403
battery type:            LION
OEM info:                SANYO

Aleksey Nogin: it seems that it's not a bug in KDE, but more in bios or kernel!
Gerald Teschl: i will try to reproduce it on my laptop, but it looks like a bug
in KDE!

It looks like after a reboot it will handle the two batteries case fine
here. (/proc/acpi list correct values for me)

Gerald Teschl: it handles 2 batteries fine on my laptop.
I think i can close this bug as NOTABUG, because it's really not a bug here.