GNOME Bugzilla – Bug 435036
crash in Network Manager: Trying to switch from wired to wireless using iwlwifi (ipw3945 works fine)
Last modified: 2007-12-26 10:30:10 UTC
What were you doing when the application crashed? Trying to switch from wired to wireless Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:17:55 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 386138112 vsize: 386138112 resident: 17571840 share: 12238848 rss: 17571840 rss_rlim: 18446744073709551615 CPU usage: start_time: 1178057292 rtime: 154 utime: 133 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nm-applet' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912676967696 (LWP 3036)] (no debugging symbols found) 0x00002aaab050f83f in waitpid () from /lib64/libpthread.so.0
+ Trace 131773
Thread 1 (Thread 46912676967696 (LWP 3036))
----------- .xsession-errors (460 sec old) --------------------- File "/usr/bin/puplet", line 355, in run self._getOnDbus() File "/usr/bin/puplet", line 229, in _getOnDbus "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__ _dbus_bindings.UInt32(0)) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__ reply_message = self._connection.send_message_with_reply_and_block(message, timeout) dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files ** Message: <info> You are now connected to the wired network. ** Message: <info> You are now connected to the wired network. --------------------------------------------------
*** Bug 437215 has been marked as a duplicate of this bug. ***
*** Bug 437231 has been marked as a duplicate of this bug. ***
*** Bug 437368 has been marked as a duplicate of this bug. ***
*** Bug 437369 has been marked as a duplicate of this bug. ***
*** Bug 437650 has been marked as a duplicate of this bug. ***
*** Bug 437838 has been marked as a duplicate of this bug. ***
*** Bug 438450 has been marked as a duplicate of this bug. ***
*** Bug 440419 has been marked as a duplicate of this bug. ***
*** Bug 440756 has been marked as a duplicate of this bug. ***
*** Bug 442317 has been marked as a duplicate of this bug. ***
*** Bug 442373 has been marked as a duplicate of this bug. ***
*** Bug 442861 has been marked as a duplicate of this bug. ***
*** Bug 443109 has been marked as a duplicate of this bug. ***
*** Bug 443110 has been marked as a duplicate of this bug. ***
*** Bug 443111 has been marked as a duplicate of this bug. ***
*** Bug 443186 has been marked as a duplicate of this bug. ***
*** Bug 443200 has been marked as a duplicate of this bug. ***
*** Bug 443429 has been marked as a duplicate of this bug. ***
Reverting to ipw3945 codebase has resulted in no further oopses or crashes. it would seem that the iwlwifi codebase shipped with Fedora 7/Rawhide is the cause of these errors.
Aha! Good to know! Can others confirm this?
Hi Chris There are lot of people reporting this in the #fedora channel on freenode. Up|down|crossgrading to the ipw3945 seems to fix their problems. There is also a Redhat bug (I don't have number with me) where they discuss this exact behaviour, and the best way to fix it (which was closed about 12 days ago without a resolution).
*** Bug 444347 has been marked as a duplicate of this bug. ***
*** Bug 444498 has been marked as a duplicate of this bug. ***
*** Bug 444232 has been marked as a duplicate of this bug. ***
*** Bug 444188 has been marked as a duplicate of this bug. ***
*** Bug 444305 has been marked as a duplicate of this bug. ***
*** Bug 443949 has been marked as a duplicate of this bug. ***
We need to get somebody to install NetworkManager-debuginfo to get better backtrace here...
*** Bug 443284 has been marked as a duplicate of this bug. ***
*** Bug 444319 has been marked as a duplicate of this bug. ***
I just got my hands on a Toshiba Tecra laptop which has a 3945. Using iwl3945, I'm able to connect to wireless networks no problem without any crash. Is there something specific I need to do to reproduce this?
*** Bug 444530 has been marked as a duplicate of this bug. ***
Created attachment 89446 [details] Backtrace with debuginfo symbols
Okay, I finally managed to get this to be reproducible. From what I can tell, this is only reproducible before scan results have come in, e.g. if there are no available networks in the drop down list. At that point, simply attempting to connect to any network via "Connect to other network" will cause this crash.
*** Bug 445618 has been marked as a duplicate of this bug. ***
*** Bug 445688 has been marked as a duplicate of this bug. ***
*** Bug 445935 has been marked as a duplicate of this bug. ***
Fixed in network-manager-applet SVN revision 80. There was no prototype for wso_wpa_create_phase2_type_model(), causing GCC to cast the returned pointer back to an int when called. Caused segfaults on 64-bit platforms.
Submitted to Fedora updates-testing. For now, people can get fixed builds at http://www.gnome.org/~caillon/temp/ (will be removed when the builds make it to F-7 updates)
If someone can confirm the new build fixes the crash, that would be great.
*** Bug 446541 has been marked as a duplicate of this bug. ***
*** Bug 446657 has been marked as a duplicate of this bug. ***
*** Bug 446958 has been marked as a duplicate of this bug. ***
I updated to the new network manager rpm's provided here http://www.gnome.org/~caillon/temp/ to my fedora 7 final release. Then I booted. And this time my access point was found as soon as I logged in (wasn't so earlier) and it asked me the keyring-password which I provided. After that it showed these messages in the logs: [root@localhost ~]# tail -f /var/log/messages Jun 14 18:36:48 localhost NetworkManager: <info> SUP: response was 'OK' Jun 14 18:36:48 localhost NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Jun 14 18:36:48 localhost NetworkManager: <info> SUP: response was 'OK' Jun 14 18:36:48 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 14 18:36:49 localhost kernel: iwl3945: REPLY_ADD_STA failed Jun 14 18:36:54 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Jun 14 18:37:08 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long (>20s), asking for new key. Jun 14 18:37:08 localhost NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'BSNL'. Jun 14 18:37:12 localhost kernel: iwl3945: ipw going down Jun 14 18:37:12 localhost kernel: iwl3945: Grabbing access while already held at line 825. It stopped and asked me to provide the network key. I provided it. After providing the network key. Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) New wireless user key for network 'BSNL' received. Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 14 18:38:25 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'BSNL' is encrypted, and a key exists. No new key needed. Jun 14 18:38:27 localhost NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0 Jun 14 18:38:27 localhost NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0 Jun 14 18:38:28 localhost NetworkManager: <info> Error opening supplicant global control interface. Jun 14 18:38:28 localhost NetworkManager: <WARN> real_act_stage2_config(): Activation (wlan0/wireless): couldn't connect to the supplicant. Jun 14 18:38:28 localhost NetworkManager: <info> Activation (wlan0) failure scheduled... Jun 14 18:38:28 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 14 18:38:28 localhost NetworkManager: <info> Activation (wlan0) failed for access point (BSNL) Jun 14 18:38:28 localhost NetworkManager: <info> Activation (wlan0) failed. Jun 14 18:38:28 localhost NetworkManager: <info> Deactivating device wlan0. Jun 14 18:38:34 localhost NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0 Jun 14 18:38:34 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jun 14 18:38:34 localhost NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0 Jun 14 18:38:54 localhost NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. And no results. I was not connected. What should you say ?
Well, it didn't crash so I would say this specific bug about the crash is fixed for you. Sounds like a different bug about getting it to connect, though. Looking at the logs, it appears you also need to update the supplicant. yum update wpa_supplicant
*** Bug 447662 has been marked as a duplicate of this bug. ***
*** Bug 449561 has been marked as a duplicate of this bug. ***
*** Bug 440659 has been marked as a duplicate of this bug. ***
*** Bug 455091 has been marked as a duplicate of this bug. ***
*** Bug 458562 has been marked as a duplicate of this bug. ***
*** Bug 459179 has been marked as a duplicate of this bug. ***
*** Bug 459797 has been marked as a duplicate of this bug. ***
*** Bug 462729 has been marked as a duplicate of this bug. ***
*** Bug 466304 has been marked as a duplicate of this bug. ***
*** Bug 467818 has been marked as a duplicate of this bug. ***
*** Bug 468829 has been marked as a duplicate of this bug. ***
*** Bug 474389 has been marked as a duplicate of this bug. ***
*** Bug 475128 has been marked as a duplicate of this bug. ***
*** Bug 476285 has been marked as a duplicate of this bug. ***
*** Bug 480458 has been marked as a duplicate of this bug. ***
*** Bug 492747 has been marked as a duplicate of this bug. ***
*** Bug 492750 has been marked as a duplicate of this bug. ***
*** Bug 492751 has been marked as a duplicate of this bug. ***
*** Bug 493470 has been marked as a duplicate of this bug. ***
*** Bug 505429 has been marked as a duplicate of this bug. ***