https://bugs.kde.org/show_bug.cgi?id=379516
--- Comment #17 from Michal Kec (MiK) <k...@kecnet.cz> --- Hallo Méven, thank you for your valuable input! I believe this can be just a packaging issue. How can I help to find it out? Since I just installed libkf5solid-bin 5.65.0-0xneon+18.04+bionic+build28, the result of the command is: [mik@desktop ~]$ solid-hardware5 query "[StorageVolume.ignored == false OR StorageAccess.ignored == false]" udi = '/org/kde/fstab/server:/mnt/public' udi = '/org/kde/fstab/server:/mnt/audio' udi = '/org/kde/fstab/server:/mnt/video' udi = '/org/kde/fstab/server:/var/www' udi = '/org/freedesktop/UDisks2/block_devices/dm_2d1' udi = '/org/freedesktop/UDisks2/block_devices/dm_2d0' udi = '/org/freedesktop/UDisks2/block_devices/nvme0n1p3' udi = '/org/freedesktop/UDisks2/block_devices/nvme0n1p2' udi = '/org/freedesktop/UDisks2/block_devices/nvme0n1p5' So far so good. It turns out there are two commands with two different outputs now. First the command solid-hardware5 here. Then the command solid-hardware I've used in the previous comment (including all loop devices). Maybe my Krusader uses the wrong one? How can I check or even control that? What is the role of "solid" and why do I have installed two versions? I've uninstalled the old solid-hardware command, part of the kde-runtime package (which seems to contain only KDE4 related binaries and dependencies). I've even rebooted, but Krusader still shows all loop devices. Maybe I could try to uninstall package libsolid4 to make Krusader to use libkf5solid5 instead. That package has 17 more dependencies including kdelibs5-plugins, thus I'm not sure if that won't brake the system. -- You are receiving this mail because: You are watching all bug changes.
