Package: fdpowermon Version: 1.2 Severity: normal Hi Wouter,
after nearly using up all of the battery's capacity, I put the netbook (a quite new ASUS EeePC X101, originally running Linpus/Meego) back on AC and then closed the lid to suspend it to RAM. (Not sure if I put it on AC while it was suspended or not, but it definitely was on AC when I suspended it to RAM the last time before I noticed the issue.) After the battery was fully loaded again, I disconnected the netbook from AC and then woke it up from suspend to RAM. After that, fdpowermon was displaying the wrong values. In comparison, i3tatus shows (more or less :-) correct 101.35% capacity loaded, currently discharging (awesome's ACPI widget shows about the same value) and about 3.5 hours remaining, but fdpower shows 19% capacity and 37 minutes remaining (both values are surely both wrong), discharging (which is true). It kept on displaying these wromg values constantly despite the two other tools show the decreasing available battery capacity. It was not stopped and a kill -CONT did not change the situation. Neither did suspending it and then continuing it. Killing it and starting it again helped to get back the expected behaviour. If wanted, I can provide a screenshot by private mail. P.S.: Thanks for this neat, lightweight systray ACPI tool. :-) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (900, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fdpowermon depends on: ii acpi 1.5-3 ii libgtk2-perl 2:1.223-1+b2 ii oxygen-icon-theme 4:4.6.2-2 ii perl 5.14.2-6 fdpowermon recommends no packages. fdpowermon suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
