Multiple notifications stack up and result in being displayed too late

Bug #1198144 reported by M Oberhauser on 2013-07-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Notify OSD

Bug Description

This is most notable when using the rythmbox music player. When skipping a couple of song via the "play next song" button/hotkey or clicking on another song, each time a notification is sent to Notify OSD. Not an issue but they stack up to ~30 notifications very fast and each one is displayed for a couple of seconds. So all of them are outdated as only the last one is important.

Notify OSD should drop all notifications of one category/application that aren't critical exept the last one, so that only the latest one is displayed in time.

Furthermore an option should be added to mark a notification as permanent/fixed/ageless, so it cannot be dropped in case a program requires that behaviour.

-p, --permanent Cannot be dropped out of the notification stack
-f, --fix
-al, --ageless

Of course you could invert that behaviour, so that by default all notifications are stacked and the specific ones require a parameter to be able to dropped out of the stack. In this case the rythmbox plugin has to include the new parameter.

M Oberhauser (zomtir) on 2013-07-05
description: updated
M Oberhauser (zomtir) wrote :

I should note that this is not an issue of rhythmbox! No application can forsee the user or device inputs, therefor it needs to be handled in Notify OSD.

This is a spam protection as well by the way.

M Oberhauser (zomtir) wrote :

Bug #506562 is related, it suggests to discard all notifications as soon as the application is focused.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers