*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The Hard Disk Activity doesn't read any activity on my hard drive. It is an eMMC/NAND internal storage device, seen as /dev/mmcblk0 STEPS TO REPRODUCE 1. Add Hard Disk Acivity widget to desktop, or just open plasma-systemmonitor and look at the Hard Drive entry 2. Notice there is no activity regardless of what system is actually doing. 3. OBSERVED RESULT No Activity EXPECTED RESULT Visible Activity SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Endeavor OS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION
I wanted to add that when I have mounted an sd card locally as well as sshfs for remote and they both show activity on the widget. It's only when my actual internal storage "/dev/mmcblk0" is being accessed that it does not.
Still exhibiting the behavior after the latest update
Is the drive listed as part of the sensors if you configure the applet? If not, we'll need the output of `solid-hardware6 query "[IS StorageAccess AND IS StorageVolume]"` to start with. If it is, we'll need the output of `cat /proc/diskstats`.
The drive is not listed in the configuration of the applet. Here is the info requested: solid-hardware6 query "[IS StorageAccess AND IS StorageVolume]" udi = '/org/freedesktop/UDisks2/block_devices/mmcblk0p1' udi = '/org/freedesktop/UDisks2/block_devices/sda1' udi = '/org/freedesktop/UDisks2/block_devices/mmcblk0p2' cat /proc/diskstats 179 0 mmcblk0 447158 55080 58006721 431408 268718 133552 19730991 1225184 0 398432 1667486 810 36 71405048 3950 22654 6944 179 1 mmcblk0p1 262 4065 17261 226 14 0 19 29 0 182 337 13 4 1711600 80 0 0 179 2 mmcblk0p2 446779 51015 57984772 431127 268703 133552 19730972 1225154 0 441724 1660151 797 32 69693448 3869 0 0 179 8 mmcblk0boot0 1 0 256 2 0 0 0 0 0 2 2 0 0 0 0 0 0 179 16 mmcblk0boot1 1 0 256 2 0 0 0 0 0 3 2 0 0 0 0 0 0 8 0 sda 338 0 17288 353 0 0 0 0 0 299 353 0 0 0 0 0 0 8 1 sda1 29 0 2088 34 0 0 0 0 0 31 34 0 0 0 0 0 0
Created attachment 174222 [details] attachment-2689246-0.html Done. On Mon, Sep 30, 2024 at 4:59 AM Arjen Hiemstra <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=491803 > > Arjen Hiemstra <ahiemstra@heimr.nl> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #3 from Arjen Hiemstra <ahiemstra@heimr.nl> --- > Is the drive listed as part of the sensors if you configure the applet? If > not, > we'll need the output of `solid-hardware6 query "[IS StorageAccess AND IS > StorageVolume]"` to start with. If it is, we'll need the output of `cat > /proc/diskstats`. > > -- > You are receiving this mail because: > You reported the bug.
There was another update, but the issue remains....