The indicator graph dose not go down to minimum
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-cpufreq |
Fix Released
|
Undecided
|
Unassigned | ||
indicator-cpufreq (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The indicator graph dose not go down to minimum even if the cpu is at the lowest frequency.
My cpu is Intel(R) Core(TM)2 Duo CPU E8400
Output from cpufreq-info:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 2.00 GHz - 3.00 GHz
available frequency steps: 3.00 GHz, 2.67 GHz, 2.33 GHz, 2.00 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 2.00 GHz and 3.00 GHz.
current CPU frequency is 2.00 GHz.
cpufreq stats: 3.00 GHz:23.78%, 2.67 GHz:1.72%, 2.33 GHz:1.82%, 2.00 GHz:72.68% (2226)
Related branches
Changed in indicator-cpufreq: | |
milestone: | none → 0.2 |
Changed in indicator-cpufreq: | |
status: | New → Confirmed |
Changed in indicator-cpufreq: | |
status: | Confirmed → Fix Committed |
Changed in indicator-cpufreq: | |
status: | Fix Committed → Fix Released |
This bug was fixed in the package indicator-cpufreq - 0.2-0ubuntu1
---------------
indicator-cpufreq (0.2-0ubuntu1) raring; urgency=low
* New upstream release (LP: #1105609):
- App ported to Python 3.
- Fixes LP: #1008438.
- Fixes LP: #1079864.
- Translation updates.
* debian/copyright format updated.
* Manually build py3 binary in debian/rules.
* Fix remaining lintian warnings (LP: #1082259).
-- Artem Popov <email address hidden> Fri, 25 Jan 2013 21:47:41 +0700