https://bugs.kde.org/show_bug.cgi?id=453894
--- Comment #4 from Julius R. <c3i8zv...@mozmail.com> --- 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.
