Hopefully this is the correct place to report this. I have a USB stick with two partitions - one is a DD burnt install ISO/rescue image for linux, and the second is a general fat32 partition for just file transfers. When I insert the USB flash drive into my computer (both Laptop and Desktop) I get the notification that it has been inserted, but the popup only shows the first partition (rescue disk ISO), and does not show the second fat32 partition. I can manually mount the send partition, but I think if a USB drive is inserted with multiple partitions they should all be visible in the GUI.
What KDE Frameworks version is this? Did this happen only recently or for a while? Can you check solid-hardware5 for me? Use solid-hardware5 list to find your device and then paste the output of solid-hardware5 details /org/freedesktop/UDisks2/drives/YourFlashDrive and also preferably the block devices on that device, like solid-hardware5 details /org/freedesktop/UDisks2/block_devices/sdc sdc1, sdc2, and whatever they are called. This should give hopefully give us a bit of an insight as to why they're not shown (there's an "ignored" attribute) Thanks!
If you can provide the information requested in comment #1, please add it.
Latest on Arch (same with Plasma version + applications). Attached log output - looks like the ignore attribute is set on the second partition, lol. Also, want to apologize for taking so long to get back and update this issue.
Created attachment 111570 [details] Outputs
BTW, I think what happened was this: I had flash a USB live image that also created its own tiny vfat UEFI boot partition. I think my wife then plugged it in Windows and starting using it - which could only see the hidden UEFI partition or something like that.
Your sdb2 partition has StorageAccess.ignored = true (bool) StorageVolume.ignored = true (bool) Can you provide the output of the following command? qdbus --system org.freedesktop.UDisks2 /org/freedesktop/UDisks2/block_devices/sdb2 org.freedesktop.UDisks2.Block.HintIgnore If that is "true" then the *system* tells us to ignore the device, not something we can do about on our side. Perhaps also check sdb1