Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
power applet without charge time estimates
Conversation with rdieter:
charging , time to full 1.1 hours
[23:29] <marvellous> in upower -d, charging (only) in applet
[23:30] <rdieter_laptop> ah, so lack of estimated time is all?
[23:31] <marvellous> in applet, yes
[23:31] <marvellous> I can see, Show charge information option in battery monitor settings, but nothing happens when I turn it on or off
[23:32] <rdieter_laptop> that option toggles whether to display current % charge or not
[23:33] <rdieter_laptop> on the systray icon
[23:33] <rdieter_laptop> ok, I can confirm estimated time isn't being shown for me either.
[23:33] <rdieter_laptop> charging or discharging estimates. :(
[23:34] <marvellous> In that case current % charge on the systray icon does not work as well
[23:34] <rdieter_laptop> odd, another bug? :( (works for me, fwiw)
[23:35] <rdieter_laptop> ah, seems to work only when "show state for each battery" is unchecked
[23:38] <rdieter_laptop> bug summary: update to 4.7.3, power applet lost charge/discharge time estimates
Known problem :) Fix coming soon
kdebase-workspace-4.7.3-9.fc16 has been submitted as an update for Fedora 16.
Hrm, I'm testing kdebase-workspace-4.7.3-9.fc16 here currently, still not seeing any time estimates.
I'll up to -12, and restart my session to be doubly-sure.
OK, I think I'd forgotten to restart my session, I see time estimates now in the battery applet popup (after clicking on it, not the mouse-over tooltip, to be clear)
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kdebase-workspace-4.7.3-12.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
kdebase-workspace-4.7.3-12.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.