"Hm, why is notify-osd rendering this notification as a dialog box? it's just a simple notification, it doesn't have actions..."
This is not because it has any non-default timeout, and it's not because the notifications are queued. It's almost cerainly because gnome-mount sets expire_timeout to 0, which means that the developer does not want the notification to expire by itself, as all Notify OSD bubbles do. <https://wiki.ubuntu.com/NotifyOSD#org.freedesktop.Notifications.Notify> So yes, gnome-mount should use a progress window instead, as I said yesterday. I'll provide a mockup of that today. (I'll also add text to the notification design guidelines about not using notification bubbles to show progress; that's never been a good idea, and Notify OSD just makes that more obvious.) ** Changed in: notify-osd Status: Confirmed => Invalid -- "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: Invalid 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
