Notify OSD should expire notifications when app goes off DBus
Bug #336950 reported by
Ted Gould
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| notify-osd (Ubuntu) |
Confirmed
|
Wishlist
|
Mirco Müller | ||
Bug Description
Notify OSD should watch the different clients that sent notifications on DBus. If the client drops off DBus Notify OSD should expire the notifications more quickly than it would otherwise. In many cases this is because the application has crashed or been closed explicitly. All of the notifications can't be destroyed because in many cases the notification could be sent by notify-send which exits immediately, and would be detected as leaving the bus. I would suggest limiting the number to 2, and expiring those quickly if the application leaves the bus.
| Changed in notify-osd: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
Revision history for this message
| Michaël Vanderheeren (michael-vanderheeren) wrote | #1 |
| Changed in notify-osd: | |
| assignee: | nobody → Mirco Müller (macslow) |
Revision history for this message
| Amargor (lobogris-712) wrote | #2 |
Revision history for this message
| Amargor (lobogris-712) wrote | #3 |
| affects: | notify-osd → notify-osd (Ubuntu) |
To post a comment you must log in.
In some way there should be a list of the notifications then, that can be searched fast, and the notification be removed when the application quits. This requires a lot of changes I think, because notify-send is used now...