Consistent Volume "Safe to remove" notifications
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Invalid
|
Undecided
|
Unassigned | ||
gvfs |
Invalid
|
Medium
|
|||
notify-osd (Ubuntu) |
Invalid
|
Wishlist
|
Mirco Müller |
Bug Description
At present when a hard drive partition/USB pendrive/external drive is unmounted , safe removal notification is displayed inconsistently. Before the safe removal notification there is a notification that the "writing data to drive is still going on and to wait". But sometimes this wait notification is skipped since the small write operation was over very quickly. So this leads to the user being presented with ONLY the safe removal notification , thus the user is not notified about delay due to the write operation.
But when there is no pending write operation, to delay the unmount, the user is not presented with any notification about safe-removal.
This causes confusion in the regular non-technical user/new users to Ubuntu , who usually keep waiting for the safe removal notifications to remove the drive or leads them to double-check the mount status of the drive before removing the drive
This confusion can be avoided by presenting the "Safe to remove" notification AT EVERY unmount. And this could be done elegantly using the notify-osd notifications for every volume unmount regardless of the delays. The "Wait" notification can also be done using the notify-osd. Since both these notifications don't require user interactions.
Changed in hundredpapercuts: | |
status: | New → Triaged |
Changed in hundredpapercuts: | |
milestone: | none → round-2 |
Changed in gvfs: | |
status: | Unknown → New |
Changed in gvfs: | |
importance: | Unknown → Medium |
affects: | notify-osd → notify-osd (Ubuntu) |
Changed in gvfs: | |
status: | New → Invalid |
I would really like to see this too, but have one further remark.
I think the best way to show this is to use notify-osd for the "wait"- notification, and just transform this into the "save removal" -notification when its ready. No need to show two notifications here.