| Summary: | Useless display of system load (and network usage) in widget | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | Peter Lemken <df5jt> |
| Component: | Plasmoid / Applet | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | groot, johnflux |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandriva RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
htop shows little load
System Monitor widget shows high load |
||
|
Description
Peter Lemken
2009-11-24 21:04:00 UTC
Created attachment 38546 [details]
htop shows little load
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.
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. 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? 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. 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! 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! Closing this as "applies to KSysGuard from KDE4 times". If the issue still exists for the current version, please file a new one. |