Comment 69 for bug 531190

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

Yeah I tried that in console mode (I also had the upower_0.9.5-4_i386.deb) but
my NIC did not seem to be up, so It could not connect to the repository.
Thanks for your suggestion I did not know that --force option.

2011/2/3 Rafael Reggiani Manzo <email address hidden>

> This worked fine for me (--force-overwrite because on my 10.10
> upower_0.9.5-4_i386.deb is installed):
>
> sudo dpkg --force-overwrite -i upower_0.9.1-1.2_i386.deb
>
> Also, instead of reinstall your ubuntu, you tried the following?
>
> sudo apt-get install upower
>
>
> As a first feedback, during all day on my UNR 10.10 (Acer NAV50) it's
> working very well!
> The only issue I noticed is that when I turn on the computer it doesn't
> identify that I'm using the battery. I need to start it using AC and after
> unplug it, so it identify that i'm using my battery.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (666330).
> 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
>