Bugzilla – Bug 268277
Network Manager: No reconnect to WLAN possible if connection lost
Last modified: 2008-03-22 09:40:59 UTC
This is regarding an FSC Amilo Si 1520 Notebook with Intel ipw3945 WLAN, running openSuSE 10.3 aplpha3plus. When booting the system a WLAN connection is made, after unlocking the keyring. If that connection is lost, no reconnect is possible. The Network Manager keeps coming back, asking for the passphrase for network '%s'. Only cure I found so far is reboot or falling back to ifup rather than Network Manager.
Created attachment 134519 [details] Screenshot of message box asking for passphrase
Another 3945 bug.
What makes you think it's "Another 3945 bug" ? The ipw3945 seems to work rather well and, as explained above, using ifup and wpa_supplicant there are no problems in connecting. From my perception it's another Network Manager bug.
Actually it seems that Network Manager doesn't like special characters in SSIDs. After having lost nm-applet, I restarted it from a terminal with nm-applet & Inadvertently I thus got the output from nm-applet. Every time I try to connect to >manus manum lavat< I get the message box asking for the passphrase for network '%s' while the terminal shows: (nm-applet:7165): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 3 char 96: ''' is not a valid character following a '<' character; it may not begin an element name ** (nm-applet:7165): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.DBus.Error.LimitsExceeded) The maximum number of pending replies per connection has been reached ** (nm-applet:7165): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.DBus.Error.LimitsExceeded) The maximum number of pending replies per connection has been reached Trying to activate any other listed network, results in the same message box, yet displaying the proper network name rather than '%s'
It might be of little help but of some interest to you that this works with Ubuntu 7.04 Live CD. Connecting to any network and reconnecting to any previous network works flawless using Network Manager. ;-)
I had the refusal to connect problem as well as "lockup" (machine freeze, kernel crash) when using 3945 WLAN. I found this report on the latest ipw3495 Apr 29 2007 Changes in 1.2.1 * Fix driver not make associate request when required * Fix iwconfig essid any doesn't associate problem * Fix ipw_associate_network() debug log bug * Fix ifconfig reports Link-encap as Ether (thanks to Jason) * Fix soft lockup during driver load time * Add Makefile warning if a different SHELL other than bash is used * Use the correct variable to print the direct scan essid * Fix a kernel Oops bug #1248 * Fix hardware/software RF kill switch problem during module loading time I fixed ipw3945 rpm to use this, rebuilt, installed. All my wireless problems and machine lockups are gone. I suggest you start using this version of the driver.
Re: Comment Comment #6 Latest Version according to YaST is ipw3945-kmp-default 1.2.0_2.6.21_10.3, the described problem is not ipw3945 driver related at all, since connect / reconnect works perfectly well when ifup/wpa_supplicant is used. As you may have noticed I reported the Bug against GNOME because of that.
The part "asking for the passphrase for network '%s'." is a Bug in it's own right and it's an upstream problem as well, as this happens in Fedora and Sabayon also. The rest seems to be a struggle for the password, to me it looks as though the Network Manager can't get at the Keyring successively. As is, switching between several APs is practically impossible with NetworkManager. The only way to get back in so far is reboot or service network restart umpteen times.
I see similar problems in Factory which didn't seem to exist in 10.2 Basically my wireless never works first go on resume from disk or on first boot. I always need to sux to root and rcnetwork restart. Sometimes this doesn't work and I have to rcnetwork stop... wait 5 sec ... rcnetwork start at which point it works fine. I have an Thinkpad R50e with ipw2200 and am using KDE and NetworkManager on latest Factory.
Looks like a dupe of 232420 and possibly 255765. JG, can you give us an assessment on this one?
May be the same problem as bug 255765. 10.3 has ipw3945-1.2.2 now, would be interesting to know whether this fixes the problem.
Ok, CJP, does this help? Gary, I assume you might of had the issue as well.
No. I don't think I've seen this issue, at least not recently.
I'm having similar problems. My machine is a Siemens/Fujitsu laptop, accessing the wlan by means of ipw3945 too. I'm using OpenSuSE 10.3 (final version). What happens: NetworkManager succeds in connecting to wlans with WPA encryption scheme. When connecting to a specific WEP protected wlan, I sometimes get connected and sometimes not, maybe due to the weakness of signal. When I try to reconnect later, nearer of the source, NM refuses to connect. But I have another problem: NM absolutely refuses to connect to unprotected networks.
Created attachment 181223 [details] Log file for Network Manager Showing how Network Manager fails to connect to an unprotected wlan.
Please don't report random other bugs here (connection issues to unprotected networks). As for the original bug, is it fixed now (based on comments #11, #12, #13)?
@JPR: Access Denied You are not authorized to access bug #255765. This surely does not help ;-)
Sorry, didn't notice that. I asked to be able to share the packages from that with the resort of the world, we'll see how it goes.
Could be fixed though. I just switched the wlan off and ob again. It automatically reconnected properly. rpm -q NetworkManager NetworkManager-0.7.0-35
Closing as per Comment#19