Bug 169913

Summary:	ksysguard system monitor network
Product:	[Unmaintained] ksysguard	Reporter:	Golodh <kdebugs.3.golodh>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	mail
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Golodh 2008-08-27 08:00:08 UTC

Version:           version 4 (KDE 4.04) (using KDE 4.0.5)
Compiler:          precompiled package SuSE 11.0 
OS:                Linux
Installed from:    SuSE RPMs

Ksysguard (or System Monitor; name is unclear) is a KDE application that displays e.g. system load, memory used, etc.

The application works as far as the predefined displays "process table" and "sensor load" are concerned.

The application also works when I add a custom worksheet with things like "memory".

Unfortunately it does not work (in the sense that it displays no values at all) when I drop sensors like "disk throughput" or "network IO".

I checked the scaling and it's set to "autodetect".

My KDE version is 4.0.4 (the KDE bug report wizard wouldn't let me select that) as installed by SuSE 11.0. I have simply accepted the SuSE default installation and changed nothing. I have downloaded all automatically selected SuSE patches at the date I report this.

It looks as if KSysguard (or "System monitor" or what its proper name is) works, but that it's not getting any data on disk IO or network IO.

Comment 1 Golodh 2008-08-27 08:03:00 UTC

Oh yes ... the refresh frequency for the sheet is once per 2 seconds, so that can't be the problem either.

If required I can add a screenshot of the data sheet that doesn't work.

Comment 2 John Tapsell 2008-12-13 00:51:33 UTC

SVN commit 896261 by johnflux:

Try to make the data a lot more reliable.

CCBUG:177590
CCBUG:169913


 M  +24 -12    netdev.c  


WebSVN link: http://websvn.kde.org/?view=rev&revision=896261

Comment 3 Julian Steinmann 2018-02-22 10:32:04 UTC

Can not reproduce with KSysguard 5.12.1.
Probably fixed thanks to the patch from John Tapsell.