Immediately after AC unplug, upower is showing incorrect numbers for remaining time.
In my particular case, the battery is fully charged, I then unplug, and g-p-m pops up a dialog, saying that I have 3 minutes left before my battery is empty (which is obviously bogus). After a short period of time (usually a matter of 30+ secs), the values reported by upower are correct.
This might actually be a kernel/hardware problem, reporting incorrect current_now values (as shown in the referenced downstream bug reports [1][2])
Nonetheless, upower should probably workaround this by either:
a/ having some sanity checks to ignore unreasonable high/low (static) values
b/ ignore current values for say 60secs after ac unplug
c/ compute the mean values for properties like current_now and filter values which exceed a certain ratio
d/ other ideas?
Immediately after AC unplug, upower is showing incorrect numbers for remaining time.
In my particular case, the battery is fully charged, I then unplug, and g-p-m pops up a dialog, saying that I have 3 minutes left before my battery is empty (which is obviously bogus). After a short period of time (usually a matter of 30+ secs), the values reported by upower are correct.
This might actually be a kernel/hardware problem, reporting incorrect current_now values (as shown in the referenced downstream bug reports [1][2])
Nonetheless, upower should probably workaround this by either:
a/ having some sanity checks to ignore unreasonable high/low (static) values
b/ ignore current values for say 60secs after ac unplug
c/ compute the mean values for properties like current_now and filter values which exceed a certain ratio
d/ other ideas?
Please also see the relevant downstream bug reports: bugs.debian. org/cgi- bin/bugreport. cgi?bug= 571161 bugs.debian. org/cgi- bin/bugreport. cgi?bug= 574850
[1] http://
[2] http://