gutsy: networkmanager fails to connect on first attempt

[Stephen Crosby]

Confirmed for me in both feisty and gutsy. Networkmanager attempts to connect to an open WAP, but hangs indefinitely with the connection animation until interrupted. I can interrupt it by instructing it to create a 'new wireless network'. Then if I select the same open network as it had previously attempted to connect to, it connects normally.

I have gutsy now with all the latest updates as of Aug 2.

This could be a duplicate of bug #112225.

[Florian M. (flomar)]

Hi,

i have the exact same problem, and for me the update to 'network-manager 0.6.5-0ubuntu15 or above' does not solve the problem, like announced in bug #112225.
Im using the following wlan card (lspci): Network controller: RaLink RT2561/RT61 802.11g PCI
with the 'Broadcom bcm43xx' driver/firmware
At the moment i'm using network-manager 0.6.5-0ubuntu16 on gutsy with the latest updates. The ESSID is encrypted only with 128bit WEP, this might be the point why it doesn't work for me especially.

Hope you can take another look at this issue,
Thanks!
flomar

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 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!