Version: unspecified (using KDE 4.7.0) OS: Linux Currently, when a device is being safely removed, while flushing the cache, there's no warning at all. On KDE SC 4.6, the system notification icon would at least spin around while the cache is being flushed. On KDE SC 4.7, there's nothing that indicates this at all. On KDE SC <= 4.5, safely removing a device would at least show the device as mounted while the cache is still being flushed. It was better than showing the device as unmounted immediately after clicking on safely remove. It is far too misleading. The lack of warning is extremely dangerous. In fact, I have corrupted my data before precisely because of this. I am not the only one who has suffered from this, but everyone I know who has used KDE SC 4.6/4.7. On Windows 7, it would at least show a dialog indicating the device is being safely removed. The user cannot be assumed to know that he/she has to wait till the device notifier pops up again before removing the device. I would suggest showing a notification to warn the user. Reproducible: Always Steps to Reproduce: 1. Mount a slow USB storage device 2. Copy a large file to it 3. As soon as the copy finishes, click on Safely Remove Actual Results: The device icon is shown as unmounted, which is wrong, it is NOT yet unmounted while the cache is still being flushed. Expected Results: The device icon shown as mounted, then show a warning through system notification indicating the cache is still being flushed. Show the device as unmounted only when the flushing has completed.
> Currently, when a device is being safely removed, while flushing the cache, > there's no warning at all. On KDE SC 4.6, the system notification icon would at > least spin around while the cache is being flushed. This should still be there; the button should still be replaced by the spinning thing… nothing changed since 4.6 > On KDE SC 4.7, there's > nothing that indicates this at all. On KDE SC <= 4.5, safely removing a device > would at least show the device as mounted while the cache is still being > flushed. It was better than showing the device as unmounted immediately after > clicking on safely remove. It is far too misleading. Again, this should not happen, and I can't reproduce. > The lack of warning is extremely dangerous. In fact, I have corrupted my data > before precisely because of this. I am not the only one who has suffered from > this, but everyone I know who has used KDE SC 4.6/4.7. On Windows 7, it would > at least show a dialog indicating the device is being safely removed. The device notifier icon turns into a green tick upon safe release of the device. Moreover, a notification can be set to show up if needed; just configure it to do so > The user cannot be assumed to know that he/she has to wait till the device > notifier pops up again before removing the device. I would suggest showing a > notification to warn the user. This is indeed a good point, and we were in fact already thinking about this.
> The device notifier icon turns into a green tick upon safe release of the > device. Moreover, a notification can be set to show up if needed; just > configure it to do so Ok, I may have missed the green tick, which should be a hint to developers that a user may not spot it easily. Also, I assume the notification you were referring to is shown only when the device is safe to be removed. It is shown by default indeed. My point is a user, especially a new user would not know what to expect while a device is being safely removed. What if the user miss the spinning icon in system notification (I did)? What if the user misses the "device mounted" icon? Not to mention the emblem that gives the hint to whether the device is mounted is so small. What I would like to see is something that tells the user the device is still being safely removed from the moment the user clicks on safely remove till it actually is properly unmounted. Only then should the usual popup that shows the device can be safely removed instructs the user to remove the device.
Ok, then this should be marked as a duplicate of #270703 Please confirm
I see this is a duplicate :) I guess I didn't use the right keywords.
*** This bug has been marked as a duplicate of bug 270703 ***