Bug 1051858 - when removing an usb stick, there's no message indicating when the device can be safely removed.
Summary: when removing an usb stick, there's no message indicating when the device can...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Holy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-12 08:43 UTC by cornel panceac
Modified: 2015-06-02 09:56 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-02 09:56:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 676125 0 None None None Never
GNOME Bugzilla 750267 0 None None None Never

Description cornel panceac 2014-01-12 08:43:22 UTC
Description of problem:
when pressing the "eject" button on nautilus, some info is written to the usb stick even if the device was used only for reading. this takes several seconds for a device used for reading, and much more for a device used for writing.
when the device can be safely removed, there's no message indicating this. it is not clear of the dissapearance of the "eject" sign in nautilus is the expected "notfiation" but, if it is, then is not enough. a real notification should pop up, and if the user is not reading it immediately, it should be available to be read later.

Version-Release number of selected component (if applicable):

$ rpm -q gnome-session
gnome-session-3.10.1-1.fc20.i686


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ray Strode [halfline] 2014-01-15 16:25:35 UTC
There's supposed to be a notification, i think, but I belive it's invoked by gvfs and provided by gnome-shell. Reassigning to GVFS

Comment 2 Fedora End Of Life 2015-05-29 10:27:27 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 cornel panceac 2015-05-30 10:24:26 UTC
In fedora 22 there is a notification warning that the device shall not be removed until writing has finished. But still there's no notification that the device can be safely removed.

Comment 4 Ondrej Holy 2015-06-01 12:56:38 UTC
You should see following notification if unmount takes more then 1.5 sec:
_("Unmounting %s\nPlease wait")
_("Writing data to %s\nDon't unplug until finished")

Consequently there is shown one from the following messages when device is already unmounted (if you didn't abort the notification about unmounting):
_("%s has been unmounted\n")
_("You can now unplug %s\n")

But you are right, that there isn't any notification if it doesn't take more then 1.5 sec (or you aborted the notification). 

Probably the second message might be shown everytime to be sure that device is unmounted...

Comment 5 Ondrej Holy 2015-06-02 09:56:21 UTC
I've already attached patch upstream to show the notification everytime...


Note You need to log in before you can comment on or make changes to this bug.