Ah ok. Well that's really a NetworkManager-only issue. notify-osd just
displays what it gets sent from applications via DBus/libnotify. So the
solutions for NetworkManager is to:
- not use a notification at all for this
- but present the user with a dialog right away
or
- hint the user with just a list of available network-cells/ESSIDs (in a
notification)
- mark or start a dialog allowing the user to take action (select the desired
network-cell/ESSID)
But this issue really has to get some input and consideration from the
design- and user-interaction team. This is one of those cases where
NetworkManager abuses notifications for user-interaction (well we got
rid of the action in the jaunty-cycle, but that was only half of the
solution), where it should have used proper dialogs form the start.
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
networkmanager + libnotify + available wireless networks = bad usability
https://bugs.launchpad.net/bugs/383404
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
