Comment 42 for bug 531190

I ran the command and nothing has changed, I get the same bogus behaviour. And for what it seems now every bug will be addressed for natty and no for Maverick. Many of my unity's bugs will never be fixed, so at least I hope that this one will or it will damage my netbook. I'm just crossing my fingers.

Este mensaje ha sido enviado gracias al servicio BlackBerry de Movilnet

-----Original Message-----
From: "B.J. Herbison" <email address hidden>
Sender: <email address hidden>
Date: Mon, 15 Nov 2010 21:58:25
To: <email address hidden>
Reply-To: Bug 531190 <email address hidden>
Subject: [Bug 531190] Re: upower (devkit-power) reporting bad data when AC
 cable is unplugged

Could someone explain the full effect of the "gconftool ..." command?
The page http://live.gnome.org/GnomePowerManager/FAQ says to use it if
my battery is faulty, but my battery gives consistent results -- except
I get the bogus alert when I disconnect the external power. (Is there
way to tell whether this is a battery glitch or a upower issue?)

I want low power alerts when my battery runs down, just not the bogus
report. I'm worried that I will lose the correct alerts if I use the
"gconftool ..." command.

Ubuntu 10.10, Dell Studio laptop.

--
upower (devkit-power) reporting bad data when AC cable is unplugged
https://bugs.launchpad.net/bugs/531190
You received this bug notification because you are a direct subscriber
of a duplicate bug (666330).

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 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