[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #5 from Julius R. --- Let me rephrase that: Unmounting drives with one click, is convenient - if the user knows what he is doing. For example, by triggering the context menu. Unmounting drives with one click by accidently (!) clicking on a pictogram, can be a problem. Imho :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #4 from Julius R. --- Yes, it did. This is a freak case, but when using synology drive client on a mounted drive (synchronisation tool for a local or remote NAS) and the local source gets unmounted while the app is running, it acknowledges the emptiness as a command to delete all files at target. This is, obviously, unwanted behaviour and a critical bug within the synology software. But I stand by my point, a locally mounted drives should not be dismounted without confirmation. It must not always be critical, it could also be simply inconvenient. Imagine this use case: A user has an encrypted drive. For dual-boot purposes, this is done with veracrypt. The decrypted drive will now appear as mounted device. On this drive, the user stores config files from mozilla, work files, sensible settings from other programs etc etc. If this drive can be randomly unmounted by accidently clicking on it in the file explorer (dolphin), that can be quite an annoyance... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #3 from Nate Graham --- Are you 100% sure of that? Did it happen to you? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 --- Comment #2 from Julius R. --- Hi Nate, you are right, when the file process is handled by plasma, this does not pose a problem. False assumption by me, sorry. The other problems remain however: Whenever a service or third party application depends on the mounted drive "being there", an accidental unmount can lead to serious problems. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453894] Eject Symbol next to mount drives can lead to catastrophic data failures!
https://bugs.kde.org/show_bug.cgi?id=453894 Nate Graham changed: What|Removed |Added Product|dolphin |frameworks-kio Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org Resolution|--- |WAITINGFORINFO Component|panels: folders |Places CC||kdelibs-b...@kde.org, ||n...@kde.org Version|22.04.0 |5.93.0 Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- > the drive gets onhooked immediately. An ongoing copy process could lead to > data corruption. Running services relying on the drive could lead to data > corruption. That's not supposed to happen. When I copy a large file to an external drive and then click on the Eject button, Dolphin shows an error message saying, "One or more files on this device are opened in application "dolphin"." Does that not happen when you try this? Can you attach a screen recording that shows the issue happening? -- You are receiving this mail because: You are watching all bug changes.
