Oh, you are saying notify-osd turns non-default timeouts into dialog
boxes? That's wrong, since the dialog boxes won't go automatically the
same way than notification bubbles go.
Arguably the usage should be fixed in gnome-mount, but in jaunty it's
almost impossible to collect the list of applications which are affected
by this (think about third-party apps).
It is gravely wrong to assume that all the software in the world will
instantly follow the semantics of notify-osd. This can be done
eventually, after a couple of cycles, but not immediately. Even ignoring
the timeout is better than converting it into a dialog, but for Jaunty
I'm inclined to say that we should respect the timeout, since it's
impossible to fix all applications which use timeouts in time.
** Changed in: notify-osd
Importance: Undecided => High
Status: Won't Fix => Confirmed
--
"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 Canonical's Notification Display Agent: Confirmed
Status in “gnome-mount” source package in Ubuntu: Confirmed
Status in “indicator-applet” source package in Ubuntu: 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
