Red Hat Bugzilla – Bug 817460
KDE CPU/System Monitor shows zero CPUs
Last modified: 2013-08-01 05:21:23 EDT
Description of problem:
The CPU Monitor and System Monitor plasmoids are unable to see any CPUs. They display no graphs and if you go into the settings the box where you can click on the check boxes where you choose which cores to display are not there. Just a empty box where they would be. This functionality works fine on same machine on f16.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add a CPU or System monitor plasmoid to the desktop
2. you see no cpu activity and are unable to add CPU cores to the display
no CPU activity displayed
to see the CPU activity graph
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.