SUMMARY Dolphin Removable Devices context menu needs Unmount just like the Devices context menu. Safely remove powers down and logically ejects a thumb drive requiring one to physically remove and re-insert it before use again. STEPS TO REPRODUCE 1. Right-Click on removable USB device 2. 3. OBSERVED RESULT Context menu contains: - Open in New Window - Open in New Tab - Properties - Safely Remove - <separator> - Hide - Hide Section 'Removable Devices' EXPECTED RESULT - Open in New Window - Open in New Tab - Properties - Unmount - Safely Remove - <separator> - Hide - Hide Section 'Removable Devices' SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon 5.17 (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Kernel 5.0.0-36-generic
Why would you want to unmount a USB flash drive but keep it powered on and plugged into your computer? Can you explain your use case?
Thank you for the quick reply. Yes: You want to reformat or install an ISO to a thumb drive. You plug it in, mount it, view it to be sure it's blank or doesn't contain any data you want to save, then unmount it and format it or whatever. Or you copy a file or two off of it, then hit the "Safely Remove", then realize you wanted one more file. Too bad, you have to pull it and start all over again. Clearly, one can do this from the command line, but using the GUI and a mouse has benefits. Also not all computers have easily reachable USB ports (some of us still have desktop machines). Conversely, why does a thumb drive need to be powered down at all? if it's unmounted, there's no benefit to making it inaccessible, is there?
One more possible issue: I have an older USB attached SD card reader. "Safely Remove" powers down the entire device rather than the subject SD card. In my case, the device is internally installed in a desktop machine and internally connected to a USB buss, so unplugging and plugging it back in is not an option. Either rebooting or some device power control magic if you're that familiar with the device is required. Granted, this case is a poorly designed hardware issue, but it is easily managed by a more friendly Dolphin context.
*** This bug has been marked as a duplicate of bug 402660 ***
*** This bug has been marked as a duplicate of bug 405979 ***