https://bugs.kde.org/show_bug.cgi?id=453894
--- Comment #7 from Julius R. <c3i8zv...@mozmail.com> --- Thanks for the clarification. I do believe, this bug report should be closed as resolved now? Reason: As you described KDE is aware of file operations and disallows unmounting (as it should), when there are operations running (like copying). My point is a different one: That it can lead to unwanted behaviour, if a mounted drive gets unmounted accidently, if other software relies on it. For example, a browser does not start anymore, when the config files have been stored on that particular drive, which is mounted at boot. There is also no file-operation in my case of data-loss, which was a critical bug in synologys software (I circumvented this now with a little script, that kills the synology client, whenever it detects, that the drive is no longer mounted). So, summarized a) There is no way for the system to anticipate the complications described above. They just happen and are not related to file operations. b) When the majority of users is fine with the eject icon luring dangerously over every mounted drive, folder and device - then that is the way it is and it should stay. :) Thanks Nate! -- You are receiving this mail because: You are watching all bug changes.
