Hi, everybody!
I just read the mb-status program and saw that filtering disks to monitor is a ToDo task. In the meantime, is there some patch/workaround to stop showing /dev/loop discs? I just hate them XDXDXD (not true), but they annoy me and the real important discs get lost in this list.
Sorry for the nagging, today’s my cats are inside home and they are bothering me!
1 Like
zolw
June 3, 2025, 1:34pm
2
Hi,
Consider using option -v, --invert-match select non-matching lines e.g.
df -h | grep -v -e 'loop'
I wonder why I don’t see loop devices… Are you using Snaps?
Yes.
Specially for LibreOffice, which has no Report Builder (database report builder using GUI) in crimpled version of Arch.
If I had started with snaps for that, reason, I had to keep it that way (unless AppImage us better option).
1 Like
Oh, but do you mean doing it outside the Disk Status script from mb-status?
My idea is to still use the mb-status script, that comes as nice utility, thou.
Thanks, anyway 3>
The updated script should filter out loop devices.
@lobaluna thanks for bringing this to my attention, and please let me know if it works
1 Like
Hi, @napcock .
Has the script been pushed to upstream? I still see those /dev/loop devices in Discs Status menu
napcok
June 24, 2025, 6:56am
8
Updated script is available in mabox-tools package since 25-06-04.
Can you please provide some info…
Output of few commands might help.
yay -Qa |grep mabox-tools
whereis mb-status
Also output of your df -kh might help me to test script, as i do not have any loop devices on my system. (And I don’t want to mess up my system by installing snaps.)
I’m sorry for the delay and lack of providing info, previously.
Here it is:
$ yay -Qa | grep mabox-tools
mabox-tools 20250625-1
$ whereis mb-status
mb-status: /usr/bin/mb-status /home/lobaluna/.local/bin/mb-status
$ df -kh
Filesystem Size Used Avail Use% Mounted on
dev 16G 0 16G 0% /dev
run 16G 1.9M 16G 1% /run
/dev/nvme0n1p4 89G 31G 53G 37% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 16G 18M 16G 1% /tmp
/dev/nvme0n1p1 349G 47G 284G 15% /home
/dev/loop0 128K 128K 0 100% /var/lib/snapd/snap/bare/5
/dev/loop1 56M 56M 0 100% /var/lib/snapd/snap/core18/2855
/dev/loop2 146M 146M 0 100% /var/lib/snapd/snap/blue-recorder/126
/dev/loop3 56M 56M 0 100% /var/lib/snapd/snap/core18/2887
/dev/loop4 74M 74M 0 100% /var/lib/snapd/snap/core22/1981
/dev/loop5 67M 67M 0 100% /var/lib/snapd/snap/core24/1006
/dev/loop6 74M 74M 0 100% /var/lib/snapd/snap/core22/2010
/dev/loop8 62M 62M 0 100% /var/lib/snapd/snap/ffmpeg-2404/59
/dev/loop7 67M 67M 0 100% /var/lib/snapd/snap/core24/988
/dev/loop9 62M 62M 0 100% /var/lib/snapd/snap/ffmpeg-2404/75
/dev/loop11 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198
/dev/loop10 219M 219M 0 100% /var/lib/snapd/snap/gnome-3-34-1804/93
/dev/loop12 517M 517M 0 100% /var/lib/snapd/snap/gnome-42-2204/202
/dev/loop13 506M 506M 0 100% /var/lib/snapd/snap/gnome-42-2204/176
/dev/loop14 92M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop16 1.4G 1.4G 0 100% /var/lib/snapd/snap/kf6-core24/28
/dev/loop17 333M 333M 0 100% /var/lib/snapd/snap/kdenlive/124
/dev/loop15 319M 319M 0 100% /var/lib/snapd/snap/kdenlive/120
/dev/loop18 1.4G 1.4G 0 100% /var/lib/snapd/snap/kf6-core24/30
/dev/loop19 1.1G 1.1G 0 100% /var/lib/snapd/snap/libreoffice/342
/dev/loop20 1.1G 1.1G 0 100% /var/lib/snapd/snap/libreoffice/344
/dev/loop21 208M 208M 0 100% /var/lib/snapd/snap/mesa-2404/495
/dev/loop23 51M 51M 0 100% /var/lib/snapd/snap/snapd/24505
/dev/loop25 455M 455M 0 100% /var/lib/snapd/snap/telegram-desktop/6684
/dev/loop22 291M 291M 0 100% /var/lib/snapd/snap/mesa-2404/887
/dev/loop24 51M 51M 0 100% /var/lib/snapd/snap/snapd/24718
/dev/loop26 455M 455M 0 100% /var/lib/snapd/snap/telegram-desktop/6688
tmpfs 3.1G 104K 3.1G 1% /run/user/1000
napcok
June 28, 2025, 6:09pm
10
What is this? Probably a copy of an older script version… just delete it and try again.
Oh, that was my attempt to filter the /dev/loop devices… Yes, I completely forgot about it
Of course, that fixed it immediately!
I’m sorry to be this distracted!
1 Like
Is it too much to ask if the same filter could be applied to the Places menu (super+dot)? Please, of course.
1 Like
napcok
July 13, 2025, 9:52pm
13
No problem, I will add it with next update
1 Like