Device Notifier does not obey the setting of "Removable Devices Only". See attached screenshot. (Only the first device is a removable device, the remaining four are fixed SSD/HDD drives.) Reproducible: Always Steps to Reproduce: 1. In "Device Notifier Settings -> General" set option to "Removable Devices Only" -> Apply -> OK 2. Insert a removable device. (USB stick for example.) 3. Actual Results: Device Notifier shows fixed devices as well as the just inserted removable device. Expected Results: Only the removable device is shown. KDE Frameworks 5.17.0 plasma5-workspace 5.5.2-1.1
Created attachment 96687 [details] Device Notifier ignoring setting "Removable Devices Only"
Works here. Can I see your ~/.config/plasma-org.kde.plasma.desktop-appletsrc ? Also the output of "udisksctl dump"
Created attachment 96733 [details] As requested: plasma-org.kde.plasma.desktop-appletsrc
Created attachment 96734 [details] As requested: udiskctrl dump
Requested information attached.
Both the drive on sda and sdc are both marked as ejectable by udisks. /org/freedesktop/UDisks2/drives/Corsair_Force_LS_140681530000994605e6: Ejectable: true /org/freedesktop/UDisks2/drives/WDC_WD2500AAKS_2_WD_WMART1815083: ConnectionBus: Ejectable: true From a Plasma POV we're doing the right thing with the data we're given. Please follow this up with udisks: http://www.freedesktop.org/wiki/Software/udisks/ Thanks
Hmm... yes, it seems that it was introduced with the udisks2 update to 2.1.6 I have another machine which still has 2.1.5 and that gives the following: ... Ejectable: false Id: Corsair-Force-LS-140681530000994605e6 ... I don't have plasma5 on that machine, but I'm guessing the device notifier would (correctly) not show the above drive. OK. Thanks. Sorry for the erroneous bug report.
(In reply to David Edmundson from comment #6) > Please follow this up with udisks: > http://www.freedesktop.org/wiki/Software/udisks/ Just for information. Bug report against udisks2: https://bugs.freedesktop.org/show_bug.cgi?id=93789
*** Bug 358250 has been marked as a duplicate of this bug. ***