GNOME Bugzilla – Bug 330822
Battery always reported as 0% if no information is available at startup
Last modified: 2006-02-11 20:32:28 UTC
Please describe the problem: I have a Logitech MX-1000 cordless mouse that reports battery information; however, HAL only begins reporting battery.charge_level.{current,percentage} 30 seconds after the mouse was plugged in--see <https://bugs.freedesktop.org/show_bug.cgi?id=5865>. This confuses g-p-m into thinking that the battery level is 0% forever (unless I started g-p-m after these 30 seconds). It would be nice if g-p-m would handle this more robustly. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
I have a MX-1000 also, which seems to work fine, but then I normally boot my machine with the USB already plugged in... GPM is acting as expected -- it expects the information to be stable on coldplug. The error is with the hal backend. It should not be reporting it's capability "battery" before coldplugging itself in the csr addon. As g-p-m acts only on HAL property modified events, g-p-m cannot "rescan" 30 seconds later. This has to be fixed outside g-p-m as the information could be used by other policy agents. I'll close this bug, and we'll work from https://bugs.freedesktop.org/show_bug.cgi?id=5865 Richard.