Comment 81 for bug 531190

Revision history for this message
sid (itissid) wrote : Re: [Bug 531190] Re: upower (devkit-power) reporting bad data when AC cable is unplugged

yes! what ever happened to good old sampling and running averages!?

On Fri, Apr 29, 2011 at 1:26 AM, Miroslav <email address hidden> wrote:

> I'm contributing with "me too".
>
> Running Ubuntu 10.10
>
> Take a look at attached screenshot,
> I get those spikes in the power history
> whenever I plug or unplug the power cord
> from the laptop.
> Obviously the spikes are wrong readings,
> should be filtered out by the upower
> because they screw gnome-power-manager.
>
> I suggest - whenever there is power related
> event, upower should take 3 readings of power
> consumption in the row (with slight delay) and
> should reject unusually high/low value and
> report the average of remaining 2 values.
>
>
> ** Attachment added: "lovely spikes in power history"
>
> https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190/+attachment/2095068/+files/Screenshot-Power%20Statistics%20-%20Device%20History.png
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (516023).
> https://bugs.launchpad.net/bugs/531190
>
> Title:
> upower (devkit-power) reporting bad data when AC cable is unplugged
>
> Status in DeviceKit based power management D-Bus backend:
> Confirmed
> Status in “upower” package in Ubuntu:
> Triaged
> Status in “upower” package in Debian:
> Confirmed
>
> Bug description:
> Binary package hint: upower
>
> upower reports enormous energy-rate for first time after cord is
> unplugged.
> GPM reacts on this first event not checking subsequent events.
>
> This bug is started because I found no ways to collect data for bug
> #473552.
> I have no devkit-power package.
>
> === EFFECTS ===
>
> This is the underlying cause to gnome-power-manager immediately
> reporting critical battery after unplug even while charge is good. It
> is not a gnome-power-manager problem, the root is here in upower.
> Please do not report bugs against gnome-power-manager for this!
>
> To workaround the effects execute:
>
> gconftool-2 --type bool --set /apps/gnome-power-
> manager/general/use_time_for_policy false
>
> (from <https://bugs.launchpad.net/ubuntu/+source/gnome-power-
> manager/+bug/572541/comments/1>)
>
> === apport information ===
>
> ProblemType: Bug
> Architecture: i386
> Date: Wed Mar 3 11:15:13 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/lib/upower/upowerd
> InstallationMedia: Lubuntu 10.04 "Lucid Lynx" - Alpha 3 i386 (20100225)
> Package: upower 0.9.0+git20100216.b9bb78-0ubuntu1
> ProcEnviron:
>
> ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
> SourcePackage: upower
> Uname: Linux 2.6.32-15-generic i686
> ---
> Architecture: i386
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Lubuntu 10.04 "Lucid Lynx" - Alpha 3 i386 (20100225)
> Package: upower 0.9.0+git20100216.b9bb78-0ubuntu1
> PackageArchitecture: i386
> ProcEnviron:
> LANGUAGE=en_US.UTF-8
> LANG=en_US.UTF-8
> LC_MESSAGES=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
> Tags: lucid
> Uname: Linux 2.6.32-15-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/devicekit-power/+bug/531190/+subscribe
>