I just remembered about this yesterday, and I can confirm it is showing me unknown but accessible networks.
Javier Domingo 2012/5/6 Javier Domingo <[email protected]> > 2012/5/6 Milan Bouchet-Valat <[email protected]> > >> Le dimanche 06 mai 2012 à 15:41 +0200, Javier Domingo a écrit : >> > Hi, >> > >> > >> > I don't know if the design team has thought about gnome-shell's >> > networking interface, but it is quite horrible that if you are >> > connecting to a wifi ap, you cannot switch it off it is specially when >> > the connection halts for several seconds. >> Yes, this is bug 654033 [1]. >> >> (Which has several duplicates...) >> >> > It is also annoying not having available the wired connections to >> > choose, having to wait till you plug one to select the one you want to >> > use and not being able to disable wired connections without them >> > plugged. >> Showing wired connections while no cable is plugged in means showing >> useless information most of the time, especially on laptops. If you >> connected once to a wired network, you would always have a useless "Auto >> eth 0" item, even if you connect using WiFi 364 days a year. >> >> What's the problem with selecting the network you want after or while >> the computer tries to connect to the wrong one? That doesn't slow down >> the process. >> >> Also, disabling wired connections while no cable is plugged doesn't make >> much sense to me: it has no effect if you don't plug a cable; and if you >> do plug one, you probably want to use the connection... >> >> > Last but not least, the idea of getting a totally blocking window for >> > asking for a password that is already filled in the form for a >> > wireless connection blocks the workflow, >> I find it kind of annoying too, but that's how all dialogs from the >> Shell behave. Anyway, you should only have to use it the first time you >> connect to the network. The design asks[2] that the dialog only appears >> in response to user action, so it shouldn't be disruptive. >> > > Not really, after I suspend the laptop, and go to the train for example, > and switch it on (where the previously connected network isn't available), > I get the "Network Disconnected" notification when I have been working for > a time there, which totally interrupts what I am doing (it doesn't > happen immediately after coming back from suspension), and there starts to > ask for passwords from the inaccessible network sometimes. > > I am not too sure if it is from the inaccessible network or not, I will > take attention on that next time. > > >> > as it is also the fact that it asks for the password twice. I don't >> > know if some of these lacks of design/bugs have been fixed up already. >> This is a bug due to a fight with nm-applet. I think it's fixed in 3.4, >> but you can see [3] and [4] >> >> >> >> Hope this clarifies the whole picture... >> >> >> 1: https://bugzilla.gnome.org/show_bug.cgi?id=654033 >> 2: https://bugzilla.gnome.org/show_bug.cgi?id=664495 >> 3: https://bugzilla.gnome.org/show_bug.cgi?id=667156 >> 4: https://bugzilla.gnome.org/show_bug.cgi?id=665680 >> > > All this info clarified a lot, thank you very much Milan! >
_______________________________________________ gnome-shell-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-shell-list
