After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 570499 - Flushing Cache notification too long.
Flushing Cache notification too long.
Status: RESOLVED WONTFIX
Product: gnome-mount
Classification: Deprecated
Component: programs
unspecified
Other All
: Normal minor
: ---
Assigned To: David Zeuthen (not reading bugmail)
gnome[unmaintained]
: 578266 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-04 14:13 UTC by Jorge Castro
Modified: 2012-02-28 12:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (977 bytes, patch)
2009-04-07 16:09 UTC, Cody Russell
none Details | Review

Description Jorge Castro 2009-02-04 14:13:11 UTC
When I eject a usb key and it's still writing I get this notification:

"There is data that needs to be written to the device %s before it can be removed. Please do not remove the media or disconnect the drive."

This text seems too long for a notification, I barely could read it all. I might be a slow reader. ;)

Other information:
Comment 1 Matthew Paul Thomas (mpt) 2009-02-13 10:03:41 UTC
Also, it's bad manners for the computer to say "Please do not remove the media or disconnect the drive" when it knows very well that you already have.

Will reinserting/reconnecting actually help in this case? If so, the message should be inviting you to do that. If not, it should be advising you to check that nothing was lost, and/or advising you of the proper procedure to use *next time*.
Comment 2 David Zeuthen (not reading bugmail) 2009-02-13 20:03:13 UTC
(In reply to comment #1)
> Also, it's bad manners for the computer to say "Please do not remove the media
> or disconnect the drive" when it knows very well that you already have.

This is not the case; this notification bubble is only shown when all of these conditions are true

 - the device is still plugged in

 - the user unmounts something from the user interface (I think that
   is what the reporter meant when using the word "eject")

 - it turns out the process of unmounting takes more than 0.75 seconds (e.g.
   writes are pending). 

These conditions are typically all true typically happens when the user is copying a big file to the device and then immediately unmounts the device once the copy dialog is done.

FWIW, when the unmount is complete the notification bubble changes to "It is now safe to remove the device" or something to that effect. When the device is removed, the bubble goes away.

My view is that if the user yanks the device we should just silently remove the icon etc. that was used to represent the device (or partitions on the device) and be done with it. Specifically I don't think there's any need for a lecture like this

  "Haha, you yanked the device and since our file systems suck we can't
   really handle that. Here's what you need to do next, there's this
   concept called unmounting..."
  </tongue_in_cheek>

similar to what OS X does

 http://www.askdavetaylor.com/1-blog-pics/mac-usb-device-removal-error.png

when the damage has been done already.
Comment 3 Martin Pitt 2009-02-26 13:29:58 UTC
What about shortening it to something like:

  "Writing data to %s, please do not remove it"

"remove" works equally well for removable media (card readers) as for hotpluggable devices (USB keys) IMHO.
Comment 4 Cody Russell 2009-04-07 16:07:23 UTC
*** Bug 578266 has been marked as a duplicate of this bug. ***
Comment 5 Cody Russell 2009-04-07 16:09:10 UTC
Created attachment 132279 [details] [review]
Proposed patch

I used the strings that were defined here:

https://wiki.ubuntu.com/NotifyOSD#gnome-mount

If that's not correct, let me know and I'll change it.
Comment 6 André Klapper 2012-02-28 12:30:15 UTC
"gnome-mount" will not see active development anymore according to its developers (as HAL is also dead).
Closing this report as WONTFIX - Please feel free to reopen this bug report in
the future if anyone takes the responsibility for active development again.