Summary: | USB Drive with Multiple Partitions only showing the first | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Joe <jchevarley> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | kde, plasma-bugs |
Priority: | NOR | ||
Version: | 5.11.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Outputs |
Description
Joe
2018-02-12 21:55:12 UTC
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 |