notify-osd notification urgency
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| notify-osd (Ubuntu) |
Triaged
|
Low
|
Mirco Müller | ||
Bug Description
Just noticed that the notifications may have some incorrect urgencies.
For example, if I have 6 minutes of battery power remaining, it notifies me with "normal" urgency whilst if my wireless connection is lost I'm notified with "urgent" urgency.
[Screenshot attached with wireless connected and disconnected, battery discharging and aMSN contact signed in.]
I would consider this the most correct, for this cases (current → desired):
Battery Discharging: normal → urgent
Contact signed in: normal → low
Wireless Established: low → normal
Wireless Disconnected: urgent → normal
---
notify-osd:
Installed: 0.9.24-0ubuntu2
Candidate: 0.9.24-0ubuntu2
Version table:
*** 0.9.24-0ubuntu2 0
500 http://
100 /var/lib/
| André Ventura (afv) wrote | #1 |
| Mirco Müller (macslow) wrote | #2 |
| Changed in notify-osd: | |
| assignee: | nobody → Mirco Müller (macslow) |
| importance: | Undecided → Low |
| status: | New → Triaged |
| André Ventura (afv) wrote | #3 |
| André Ventura (afv) wrote | #4 |
| affects: | notify-osd → notify-osd (Ubuntu) |
André, there are indeed bugs in the apps spitting out those notifications.
Router Disconnected as "urgent" -> ok
aMSN Pedro signed in as "normal" -> ok, but could be just low
Router Connection established as "normal" -> ok
Battery dischraging - as "normal" -> wrong, has to be "urgent", please file a bug against gnome-power-manager
We'll plan to use "100 papercuts" for such bugs during the Lucid development-cycle. I'll update the hint in the top bar of notify-osd soon to point people towards that more directly.