Bug 468216

Summary: Not all disks are shown in sensor menu
Product: [Applications] plasma-systemmonitor Reporter: John Veitch <john>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED FIXED    
Severity: minor CC: ahiemstra, Enitin, john.kizer, plasma-bugs-null, strong.drum0546
Priority: NOR    
Version First Reported In: 5.27.3   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Application window showing the problem

Description John Veitch 2023-04-06 17:09:52 UTC
Created attachment 157906 [details]
Application window showing the problem

SUMMARY
***
Not all disk drives are shown in the list of sensors.
***

I want to add a read/write sensor plasma widget to my desktop using plasma-systemmonitor widgets. The problem shows up in the main GUI application too.
My computer has 3 HDDs (sd[abc]) and 3 NVME drives (nvme0n1, nvme1n1, nvme2n1) attached. They appear in the output of `lsblk` and the KDE Sytem Info program shows them all right. However in plasma-systemmonitor when I select the Disks sensor source menu I am shown only nvme1n1p6 and nvm1 (see attached screenshot). I would expect to see all the devices listed here. nvme1n1p6 is the root partition, and "nvm1" is the label of one of the other nvme partitions, so maybe the systemmonitor is only listing those devices with labels? The others have various filesystems on them including NTFS and a ZFS pool spread over the HDDs.

STEPS TO REPRODUCE
1. Create some partitions
2. Look for them in plasma-systemmonitor

OBSERVED RESULT

All the available partitions.

EXPECTED RESULT

Only a subset of partitions.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.10, Linux 6.2.0-19-generic (kubuntu proposed but problem exists on older kernels too)
KDE Plasma Version: 5.27.3 (but has been seen in earlier versions)
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
I've been seeing this problem for a while. Maybe it is the desired behaviour but it makes it impossible to monitor all my actual disk usage.
Comment 1 Enitin 2024-03-13 17:32:51 UTC
I can confirm this problem.
I'm using a LUKS encrypted SATA SSD as an LVM cache for my LUKS encrypted SATA HDD and it's not displayed in plasma-systemmonitor.
The HDD is shown.
Comment 2 Lenzoid 2025-05-11 12:07:10 UTC
Thanks for reporting. Did any of you get the chance to retest this with the current version of KDE?
Comment 3 John Kizer 2025-05-14 19:02:14 UTC
Updating status, pending an update from the reporter here - thanks!
Comment 4 John Veitch 2025-05-16 08:05:00 UTC
I am now running KDE 6.3.5, KDE Frameworks 6.14.0, Qt 6.9.0, Linux 6.14.6. on Arch Linux.
The disks do all appear now in the system monitor options. However, they all show up as having 0 bytes/sec read rate if I add that monitor.
I am not a member of the "disk" group so perhaps this is a permissions issue?
Comment 5 John Kizer 2025-05-16 14:52:54 UTC
Thanks! Do you see a lack of read rate data for all of the drives on your device, or just the ones that previously didn't show up because they had no label?

For what it's worth, I'm not in the "disk" group on my Fedora KDE 42 device, and the Read and Write rates show up for me in System Monitor, so I don't *think* that it'd be necessary to belong to that group to have that data populate?
Comment 6 Bug Janitor Service 2025-05-31 03:47:38 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 7 John Veitch 2025-05-31 11:11:16 UTC
I went to check this today and now it seems that system monitor is able to see the read rate from all the drives.
The only thing that's changed is my kernel version, now at 6.15.0, and I doubt that has anything to do with it. I may just have been mistaken in my last report. Anyway thank you for the help.