Bug 216002 - Useless display of system load (and network usage) in widget
Summary: Useless display of system load (and network usage) in widget
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: Plasmoid / Applet (other bugs)
Version First Reported In: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-24 21:04 UTC by Peter Lemken
Modified: 2020-06-27 19:23 UTC (History)
2 users (show)

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


Attachments
htop shows little load (113.56 KB, image/jpeg)
2009-11-24 21:07 UTC, Peter Lemken
Details
System Monitor widget shows high load (3.80 KB, image/jpeg)
2009-11-24 21:09 UTC, Peter Lemken
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lemken 2009-11-24 21:04:00 UTC
Version:            (using KDE 4.3.3)
OS:                Linux
Installed from:    Mandriva RPMs

The widgets for CPU load shows a load of 100% for one of the two cores on my notebook, while htop reports practicaly no load at all. Calling ksysguard from the command line, both as root and as user, reports a CPU load of more than 50% overall load, but does not show any process that supposedly hogs my CPU.

As it is, this display is useless. I suspect that a load from one sshfs copy process that does not show up in the ksysguard display is responsible for that.

Apart from that, I find the decision not to be able to configure any System Monitors to display absolute values rather annoying and a serious regression in comparison to KDE 3.5.10. In particular the network throughput is something that I want so see in absolute values. I need to call iptraf before I know whether my line is saturated with a download and I would expect a grpahical applet to hanle this task without command line knowledge.

The old ksysguard in 3.5.10 had this feature, where you could chose between relative and absolute values for each and every sensor.

I wonder why the whole system of showing the graph in ksysguard and being able to drag and drop it into the panel has been abandoned. I find no advantages in the current setup, but dearly miss many options of the old style sysguard widgets.
Comment 1 Peter Lemken 2009-11-24 21:07:46 UTC
Created attachment 38546 [details]
htop shows little load
Comment 2 Peter Lemken 2009-11-24 21:09:04 UTC
Created attachment 38547 [details]
System Monitor widget shows high load

Also, notice the broken alignment of fonts, cutting of the first letter of each sensor.
Comment 3 Peter Lemken 2009-11-24 22:13:19 UTC
I can now confirm that it was indeed the file copy process that showed the high load. I cp'ed a file from a fuse-mount (sshfs) to a local directory and once this process was stopped, the visual load presentation went down to nil. Interestingly, an rsync does not provoke this behaviour.
Comment 4 John Tapsell 2009-11-25 12:03:27 UTC
The system load seems be correct then, if the cpu really was being used by the file copy?

So I think this bug report is just a bug report about the lack of axis, clipping text etc?
Comment 5 Peter Lemken 2009-11-25 14:02:33 UTC
Not quite. As you can see from htop (see previously attached image), processor load is well below 10%. The monitor, however, reports a value in the skies, which is incorrect.
Comment 6 Andrew Crouthamel 2018-11-02 22:56:27 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 7 Andrew Crouthamel 2018-11-16 05:23:33 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?

Thank you for helping us make KDE software even better for everyone!
Comment 8 groot 2020-06-27 19:23:05 UTC
Closing this as "applies to KSysGuard from KDE4 times". If the issue still exists for the current version, please file a new one.