https://bugs.kde.org/show_bug.cgi?id=389479
--- Comment #30 from Dmitry Khlestkov <dsx....@yandex.ru> --- Created attachment 110820 --> https://bugs.kde.org/attachment.cgi?id=110820&action=edit don't ignore storage with empty path Actually, I've added debug output to StorageAccess::isIgnored (udisks2/udisksstorageaccess.cpp): StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sdd1' path:'' (empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sdb2' path:'' (empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sdc1' path:'' (empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sda7' path:'' (empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sda6' path:'/home' (non-empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sda5' path:'/' (non-empty,ignored) StorageAccess::isIgnored udi:'/org/freedesktop/UDisks2/block_devices/sda3' path:'/boot' (non-empty,ignored) All devices that was auto-mountable before 5.43 has empty path. I've added isEmpty check and it works like a charm now. Please check the patch -- You are receiving this mail because: You are watching all bug changes.
