Bug 229357 - All disk throughput sensors give Dummy labels and no values
Summary: All disk throughput sensors give Dummy labels and no values
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-04 06:04 UTC by Marcin Gryszkalis
Modified: 2018-11-05 01:29 UTC (History)
0 users

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


Attachments
System monitor tree (36.35 KB, image/png)
2010-03-04 06:05 UTC, Marcin Gryszkalis
Details
Plot tooltip (7.14 KB, image/png)
2010-03-04 06:06 UTC, Marcin Gryszkalis
Details
Plot tooltip after ksysguard restart (11.69 KB, image/png)
2010-03-04 06:08 UTC, Marcin Gryszkalis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Gryszkalis 2010-03-04 06:04:57 UTC
Version:           4.4.0 (using KDE 4.4.0)
Compiler:          gcc 4.4.3 
OS:                Linux
Installed from:    Gentoo Packages

All sensors under "Disk throughput" behave strange. The sensors tree looks ok but when I drag the sensor (for example Disk Throughput/sda1/Rate/Read Accesses (float)) to the plot I get "Dummy" label in tooltip and the value is always 0.

It also affects related plasmoids (like complex plotter or analog meter).

It worked well in KDE 4.3.
Comment 1 Marcin Gryszkalis 2010-03-04 06:05:32 UTC
Created attachment 41310 [details]
System monitor tree
Comment 2 Marcin Gryszkalis 2010-03-04 06:06:02 UTC
Created attachment 41311 [details]
Plot tooltip
Comment 3 Marcin Gryszkalis 2010-03-04 06:08:48 UTC
Created attachment 41312 [details]
Plot tooltip after ksysguard restart

After restarting of System monitor previously added tooltips seem ok but adding another gives Dummy label again. Values are still 0 for all sensors on plot.
Comment 4 Marcin Gryszkalis 2010-03-05 17:03:15 UTC
I found following entries in messages log:

Mar  5 17:02:00 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:00 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:02 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:02 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:04 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:04 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:06 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:06 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:08 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:08 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:10 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:10 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:12 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:12 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:14 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:14 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:16 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:16 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:18 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:18 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:20 ines ksysguardd[25789]: Disk device disappeared
Mar  5 17:02:20 ines ksysguardd[25789]: Disk device disappeared
Comment 5 Marcin Gryszkalis 2010-03-05 17:29:17 UTC
I can see nothing special in /proc/diskstats
# cat /proc/diskstats | grep sd

   8       0 sda 13498980 5554356 633306549 159467761 11833980 58113866 559808432 1056400226 0 118361553 1216065276
   8       1 sda1 1065 1673 21978 11551 119 0 952 14561 0 26042 26112
   8       2 sda2 764824 3616199 35043371 13805885 706520 3687674 35155240 101378186 0 8761532 115183394
   8       3 sda3 12731580 1927631 598158288 145626553 11127341 54426192 524652240 955007479 0 114252692 1100831998
   8      16 sdb 13009497 2277503 612820557 127150979 11159166 55846994 536272488 885007340 0 107212359 1012310528
   8      17 sdb1 326 372 5672 3450 119 0 952 13003 0 16141 16453
   8      18 sdb2 58136 314791 2978331 582005 38110 1414013 11619296 3454403 0 663899 4036333
   8      19 sdb3 12950826 1961113 609825066 126562406 11120937 54432981 524652240 881539934 0 106873702 1008254624
   8      32 sdc 1225087 1836100 455718730 5557010 493215 39107339 316807760 63785883 0 7640195 69351426
   8      33 sdc1 1224242 1829002 455655186 5549038 493215 39107339 316807760 63785883 0 7632750 69343454
   8      48 sdd 1232435 1852632 459515672 5507378 493722 39107008 316807760 52495924 0 7194847 58002297
   8      49 sdd1 1231566 1845557 459452120 5499742 493722 39107008 316807760 52495924 0 7187703 57994664
   8      64 sde 0 0 0 0 0 0 0 0 0 0 0
Comment 6 Andrew Crouthamel 2018-11-02 22:53:45 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 Marcin Gryszkalis 2018-11-05 01:29:31 UTC
Seems to be fixed in (tested in 5.13.3)