Bug 374944 - KSysGuard does not show CPU/Network History graphs
Summary: KSysGuard does not show CPU/Network History graphs
Status: RESOLVED NOT A BUG
Alias: None
Product: ksysguard
Classification: Applications
Component: ksysguard (show other bugs)
Version: 5.7.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-12 06:14 UTC by h.k.ghost
Modified: 2018-01-06 11:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KSysGuard with CPU/Network History Graphs not working (39.13 KB, image/png)
2017-01-12 06:14 UTC, h.k.ghost
Details

Note You need to log in before you can comment on or make changes to this bug.
Description h.k.ghost 2017-01-12 06:14:18 UTC
Created attachment 103364 [details]
KSysGuard with CPU/Network History Graphs not working

Summary:
--------
The KSysGuard system monitor shows the CPU History and Network History widgets under the System Load tab, but they're empty; the graphs do not get displayed (i.e. no lines showing actual system stats). The Memory graph is working fine.


What I Expected to See:
-----------------------
I expected to see the graphs for CPU and Network History just like before.


Additional Info:
----------------
The app was working fine until a few days ago where I was testing a completely separate program that ended up consuming too much memory and got the entire PC to become unresponsive. (The app does not write files or anything to disk.) The display manager (sddm) crashed and restarted a few seconds later, but after this, KSysGuard stopped showing the graphs for CPU and Network history.

Properly restarting the system does not help.


OS Info:
--------
I'm using Kubuntu 16.10 AMD64
Comment 1 Gregor Mi 2018-01-05 16:35:22 UTC
Did you do an update recently? Does the problem still occur?
Comment 2 h.k.ghost 2018-01-06 10:58:21 UTC
(In reply to Gregor Mi from comment #1)
> Did you do an update recently? Does the problem still occur?

I did update, but it wasn't the updates that fixed anything. I had to reset my entire Plasma environment by removing ~/.local/ and ~/.config/ directories.

You can take a look at some of my comments in this bug report, which may provide additional info that may, or may not, be related.

https://bugs.kde.org/show_bug.cgi?id=379649
Comment 3 Gregor Mi 2018-01-06 11:15:00 UTC
Ah, it seems to be a problem with the Plasma environment and not with KSysGuard. I also understand that resetting your Plasma settings fixed this particular problem. So I close this bug now. I chose INVALID as resolution because it is not a KSysGuard bug.