network manager tries to connect to arbitrary network

Bug #157884 reported by Grzegorz
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: network-manager

After booting the system, normally network manager connects to my own secured wireless network. Normally there is no other visible vireless network. However sometimes, when some other wireless network gets activated (call it "X Network"), after booting my laptop I see message from Network Manager like "Trying to connect to X Network". And it frozens on this, and does not connect to my own network. After left-click on network manager I see two networks: my own and "X Network". X Network is selected. I try to click on my network on the list to switch to it - nothing happens, X is selected all the time and network manager still tries to connect to it.
I can only change it after some tricky combinations of deactvating wireless networks and rebooting.

Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

forgot to mention: I use Ubuntu Gutsy

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please follow the instructions at the Capture Log portion of https://wiki.ubuntu.com/DebuggingNetworkManager and add your '/var/log/syslog' file as an attachment to your bug report? Thanks in advance.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

Ok I can do it when I pick up my laptop from service :)

Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

Now I see I forgot mention one more thing: My own network is hidden - and the problem happens when some other non-hidden network appears in vicinity.

Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

It seems that this problem in the form described in the topic (connecting to arbitrary network) vanished - maybe it was fixed in some update.

Network manager is still buggy though. I have WPA Personal wireless network set up. When SSID braodcasting is enabled, everything works correctly, I never face problems - after booting the system it connects immediately.

But when SSID broadcasting is disabled, from time to time I cannot connect at all. I see the message "trying to connect to network xxx" all the time, and nothing happens, or sometimes it asks about password repeatedly, but still cannot connect. What's more, when I try to switch to other network on the list (e.g. select network yyy), after hovering over network manager icon, I still see message "trying to connect to network xxx".
This is very annoying, and because of those troubles I had to enabled SSID broadcasting again.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager:
assignee: nobody → sourcercito
importance: Undecided → Low
Revision history for this message
Basilio Kublik (sourcercito) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks again!

Changed in network-manager:
assignee: sourcercito → nobody
status: Incomplete → Invalid
Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

Sorry, I did not get notification about your previous comment.
It would be rather hard to reproduce it on live CD, because as i already mentioned, it happens only from time to time, say twice a week. I won't work on live CD so long :)
Currently I have SSID braodcasting enabled, so i cannot say if it is ok or not. I will wait a few days for Hardy realease, then upgrade, and try to disable SSID broadcasting and see how it works. If there are any issues then, I let you know.

Revision history for this message
Grzegorz (grzegorzborkowski) wrote :

I tried to do the test on my current environment (Hardy - but with kernel from previous version, because kernel from Hardy is not usable - see bug #12637).
I have now WAP Personal netowork, with MAC filtering, and with enabled SSID bradcasting. Ubuntu connects to it almost immediately after booting up.
So I disabled SSID braodcasting for testing. Network Manager did the same as previously - got lost for about 10 minutes. During this time it asked me about 4 times for the password. I typed the passwork each time, waiting, waiting, waiting, again prompt for password, waiting...... and after about 10 minutes finally it connects.
So it is still far from normal "usable" quality.
However, second laptop (Lenovo, with WinXP) was not able to connect at all to that network, so I was forced to enable SSID back. So at least it is better than Windows...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.