[Bug 391130] Re: Incorrect urgency for NetworkManager
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 appear to me as they are fine and definitely make sense for the type and likely cause of the event. I'll get around to it at some point, but if anyone has time to propose a patch that tries to keep track of notifications and back out of one if it was sent out within a specific period of time preceeding the new notification (something like within the delay for a notif. to fade out maybe?), I'll gladly review it ;) ** Changed in: network-manager (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/391130 Title: Incorrect urgency for NetworkManager -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
** 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.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
** 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-osd: - Installed: 0.9.14.1-0ubuntu1 - Candidate: 0.9.14.1-0ubuntu1 + 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 level. - Disconnecting from a network usually has a high urgency level. However, - notify-osd sometimes shows normal urgency when disconnecting from a - wired network - - How to reproduce : - - 1) Unplug the network cable, a notification appears and says Disconnected - you are now offline. This notification is urgent. == correct urgency - 2) Plug in the network cable, a notification pops-up and says Connection Established. This notification has a low urgency level. == incorrect urgency - 3) Reconnect to the network by clicking in the nm-applet from the panel and selecting (Auto eht0). A notification appears and says Disconnected which has incorerect urgency level normal. == incorrect urgency - - P.S. connecting to a network should be either urgent or normal - instead of low. - - - A screenshot is attached and the output from Terminal is: - - moo...@moomex-pc:~$ DEBUG=1 /usr/lib/notify-osd/notify-osd - ** Message: DEBUG mode enabled - - ** (notify-osd:14701): DEBUG: [2009-06-23T21:44:43-00:00, NetworkManager, id:0, icon:notification-network-ethernet-disconnected] Wired network - Disconnected - you are now offline - - ** (notify-osd:14701): DEBUG: found panel (0,0) - 1280x25 on monitor 0 - ** (notify-osd:14701): DEBUG: selecting monitor 0 at (0,0) - 1280x800 - ** (notify-osd:14701): DEBUG: top corner at: 1015, 23 - ** (notify-osd:14701): DEBUG: [2009-06-23T21:44:56-00:00, NetworkManager, id:0, icon:notification-network-ethernet-connected] Auto eth0 - Connection Established - - ** (notify-osd:14701): DEBUG: found panel (0,0) - 1280x25 on monitor 0 - ** (notify-osd:14701): DEBUG: selecting monitor 0 at (0,0) - 1280x800 - ** (notify-osd:14701): DEBUG: top corner at: 1015, 23 - ** (notify-osd:14701): DEBUG: [2009-06-23T21:45:14-00:00, NetworkManager, id:0, icon:notification-network-ethernet-disconnected] Wired network - Disconnected - - ** (notify-osd:14701): DEBUG: found panel (0,0) - 1280x25 on monitor 0 - ** (notify-osd:14701): DEBUG: selecting monitor 0 at (0,0) - 1280x800 - ** (notify-osd:14701): DEBUG: top corner at: 1015, 23 - ** (notify-osd:14701): DEBUG: [2009-06-23T21:45:17-00:00, NetworkManager, id:0, icon:notification-network-ethernet-connected] Auto eth0 - Connection Established - - ** (notify-osd:14701): DEBUG: found panel (0,0) - 1280x25 on monitor 0 - ** (notify-osd:14701): DEBUG: selecting monitor 0 at (0,0) - 1280x800 - ** (notify-osd:14701): DEBUG: top corner at: 1015, 23 + I suggest to make the networking notifications update-able, so that the right status is posted at the right time. + When the connection is established again the disconnected notification should update and write connected at exact this time. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
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 level. I suggest to make the networking notifications update-able, so that the right status is posted at the right time. When the connection is established again the disconnected notification should update and write connected at exact this time. Thanks, Jango ** Changed in: notify-osd (Ubuntu) Status: Invalid = New -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
** 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
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 thus predictable, as opposed to a disconnection, which may happen without the user's initiative. [1] https://wiki.ubuntu.com/NotifyOSD#network-manager -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 391130] Re: Incorrect urgency for NetworkManager
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
