"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.)
"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.)