Bug 334258 - CPU History and Network History are blank
Summary: CPU History and Network History are blank
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (other bugs)
Version First Reported In: 4.11.8
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-03 02:26 UTC by Donald
Modified: 2019-04-10 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Donald 2014-05-03 02:26:30 UTC
on the System Load Tab, the CPU History graphs are blank. I am running an Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz so I would expect 8 cpu graphs. None appear.

There also is two LAN cards on the machine plus a wireless card. The Network history is also blank. 

Reproducible: Always

Steps to Reproduce:
1. boot the machine and try it.
2.
3.
Actual Results:  
always the same.

Expected Results:  
I expect to see graphs of usage.

good luck. If I can tell you more, ask me.

regards
Comment 1 ttsoares 2014-09-09 13:34:45 UTC
Linux Mint here. The Network History is blank for eth0 but works for the wlan0 (wifi). This is the same behavior with Gkrellm tool. It seems that something changed inside the kernel (/proc, etc...), i am using the 3.13.0-24-generic
Comment 2 Andrew Crouthamel 2018-11-12 02:57:03 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:49:44 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Richard Llom 2019-03-11 15:03:57 UTC
(In reply to Andrew Crouthamel from comment #2)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2019-03-26 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2019-04-10 04:33:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!