Bug 405979

Summary: Places Panel should have an option to only unmount, not detach as well
Product: [Frameworks and Libraries] frameworks-kio Reporter: Andrew Shark <ashark>
Component: PlacesAssignee: KIO Bugs <kio-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: bugseforuns, kdelibs-bugs, nate, stuartksmith
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=293906
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andrew Shark 2019-03-29 03:09:09 UTC
It is impossible to unmount removable device's partition without removing device.
I was experimenting with preparing bootable usb stick, so I constantly needed mount/unmount partitions on usb stick to check bootability with qemu. It is convenient to mount a partition by just clicking to it, but the problem is that when you want to unmount it, you only have Safely Remove action. I do not know how this works internally (probably uses something like eject function of a usb device), but when you use it, device disappears from Dolphin, and next time you want to mount it, you should physically replug usb stick to your pc.

Is there a way how I can again "activate" usb stick to be shown in Dolphin without replugging physically?

I have noticed that for partitions of internal devices another function is used, which is called Unmount. Can you please implement it also for removable devices?

Workaround 1:
unmount via terminal. But it becomes uncomfortable.
Workaround 2:
add a second partition to usb stick and never mount it. When you click Safely Remove on a first partition, then both partitions disappears, but then appears again after a second. 

Operating System: Arch Linux 
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.4-arch1-1-ARCH
Comment 1 Patrick Silva 2019-03-29 09:51:40 UTC

*** This bug has been marked as a duplicate of bug 402660 ***
Comment 2 Nate Graham 2022-04-22 17:33:16 UTC
*** Bug 414906 has been marked as a duplicate of this bug. ***