registry team mailing list archive

[David Tombs <cyan.spam@xxxxxxxxx>]

Note from duplicates that this occurs often on MSI Wind laptops, but not
exclusively.

** Description changed:

  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

-- 
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 member of Registry
Administrators, which is the registrant for Debian.