https://bugs.kde.org/show_bug.cgi?id=453894
--- Comment #9 from Julius R. <c3i8zv...@mozmail.com> --- (In reply to Nate Graham from comment #8) > That shouldn't happen. Since the system is aware of open files, if you try > to unmount a disk that has open files on it, it's supposed to prevent that > from happening. If that didn't work and you were able to unmount a disk with > open files, that's a bug. That's the bug that we're tracking with this > Bugzilla ticket. More misunderstandings :) The system is surley aware of open files, there is no bug with that. It can not anticipate that files "might" be opened or accessed soon... The inconvenience I describe happens (apart from the critical synology bug), when files are not available at a specific time, due to accidently unmounting the drive. If, to give that example again, config files (the user profile) for e.g. Firefox are stored on an encrypted drive (or in a company on a network drive) - and that drive is not available due to a user accidently and unknowingly unmounting drives, then the browser gives an error: It simply can not find the user profile. There is neither file activity before or after, there are no open file activities. The problem described is btw exactly, what happenend to my mum: She accidently unmounted the drive and then didn't know, what to do. Due to the small little change of adding an unmount icon, I - personally - experienced a critical data loss (I had backups, of course). This was a bug of a third party software, that no one could foresee. On the other hand, I also had problems with a less experienced user, that did not understand the concept of mounting and unmounting - at all. Therefore, I stand by my suggestion: Network Drives and Encrypted Drives should never ever have a "quick-unmount-icon". Unlike usb flash drives (which are used only temporarily), network drives and (un)encrypted drives are (in most use cases) an integrated part of the users workflow. They need to be accessible at all times, from boot till shutdown. -- You are receiving this mail because: You are watching all bug changes.
