I have an initial version ready now. It implements the dialog layout and
workflow, but continues to use two of the upstream strings:

  Finishing up…  -> Writing data to device
  It’s now safe to eject %s-> The device %s is now safe to remove.
  It’s now safe to disconnect %s -> The device %s is now safe to remove.

Changing the strings should really be done in accordance with upstream
(see bug 329296), since doing so breaks all translations. The patch
introduces one new string ("To prevent data loss, wait until this has
finished before disconnecting."), we have to live with that.

Attaching screenshots for both dialogs.

** Attachment added: "screenshot: cache flushing"
   http://launchpadlibrarian.net/23359790/cache-flushing.png

-- 
"Writing data to device" appears as fallback alert
https://bugs.launchpad.net/bugs/332600
You received this bug notification because you are a member of Notify
OSD Developers, which is subscribed to Notify OSD.

Status in Notify OSD: Invalid
Status in “gnome-mount” source package in Ubuntu: In Progress
Status in “indicator-applet” source package in Ubuntu: Invalid
Status in gnome-mount in Ubuntu Jaunty: In Progress
Status in indicator-applet in Ubuntu Jaunty: Invalid

Bug description:
gnome-mount 0.8-1ubuntu1, Ubuntu Jaunty

When a removable storage device is taking non-trivial time to unmount (flushing 
the cache), gnome-mount puts up a "Writing data to device" notification asking 
you not to disconnect it while that's happening. Because it is persistent, 
Notify OSD renders this notification as a suboptimal fallback alert box.

Instead, gnome-mount should use a progress window containing the warning text.

It may save time to fix bug 325315 at the same time as this bug.

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

_______________________________________________
Mailing list: https://launchpad.net/~dx-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~dx-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to