Fair enough. Is there a way to track notifications sent and update the
previous disconnected one, or cancel it to show the connected within a
period of time?
Marking Triaged. I think it deserves some improvement, but generally
it's still doing the job, and the actual notification urgency levels
ap
** Tags added: notifications
--
Incorrect urgency for NetworkManager
https://bugs.launchpad.net/bugs/391130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
** Attachment added: "coming from suspend notification shows Disconnected,
although it is already established."
http://launchpadlibrarian.net/37404600/Screenshot.png
--
Incorrect urgency for NetworkManager
https://bugs.launchpad.net/bugs/391130
You received this bug notification because you
** Description changed:
- Binary package hint: notify-osd
+ Disconnecting from a network usually has a high "urgency" level.
+ However, notify-osd sometimes shows "normal" urgency when disconnecting
+ from a wired network and "low" urgency when connection is established.
- Ubuntu 9.10
- notify-
This is actually an issue of network-manager and not notify-osd itself.
Reassigned.
** Package changed: notify-osd (Ubuntu) => network-manager (Ubuntu)
--
Incorrect urgency for NetworkManager
https://bugs.launchpad.net/bugs/391130
You received this bug notification because you are a member of Ub
But there is a problem with this urgency levels:
When waking up from suspend, the notification appears saying "Disconnected" at
exact the time when wireless networking has been connected again. But the
notification for "Wlan Connected" appears a lot of time later, because it has
low urgency leve
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Low
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
--
Incorrect urgency for NetworkManager
https://bugs.launchpad.net/bugs/391130
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for reporting. The behavior you've noted is by design [1]; the
urgency level should be "urgent" only in the cases where the
disconnection leaves you with no active network connections.
As for connecting to a network, "low" is probably justified, since the
event is initiated by the user, and
** Attachment added: "notify-osd.png"
http://launchpadlibrarian.net/28248583/notify-osd.png
--
Incorrect urgency for NetworkManager
https://bugs.launchpad.net/bugs/391130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
