After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477650 - NetworkManager seems to crashes because of wpa_supplicant
NetworkManager seems to crashes because of wpa_supplicant
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-09-17 04:09 UTC by unggnu
Modified: 2008-02-15 00:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
syslog dump (32.03 KB, text/plain)
2007-09-17 04:10 UTC, unggnu
Details
Daemon.log output of error (8.52 KB, text/plain)
2007-09-18 21:55 UTC, Gavin Graham
Details
daemon.log output showing wpa_supplicant failure (2.47 KB, text/plain)
2007-09-19 02:03 UTC, Gavin Graham
Details

Description unggnu 2007-09-17 04:09:32 UTC
Steps to reproduce:
It doesn't happen on every system start but not so rare.

Stack trace:


Other information:
Sometimes after boot nm-applet is running but isn't shown in tray and wlan connection isn't established. After system reboot it works normally fine again.
I have restarted Network-Manager with "sudo /etc/dbus-1/event.d/25NetworkManager restart && sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher restart" which lets nm-applet appear in tray for some seconds but then it was vanished again.
According to syslog there was a problem with wpa_supplicant and according to ps it was still running so I killed it. After another Network-Manager restart nm-applet was shown again in tray and connection was established fine.
I am using Ubuntu Gutsy Gibbon and NetworkManager 0.6.5-0ubuntu11.
Comment 1 unggnu 2007-09-17 04:10:15 UTC
Created attachment 95702 [details]
syslog dump
Comment 2 unggnu 2007-09-17 15:57:06 UTC
Ubuntu bug entry: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/43379
Comment 3 Gavin Graham 2007-09-18 21:55:50 UTC
Created attachment 95821 [details]
Daemon.log output of error
Comment 4 Gavin Graham 2007-09-18 21:58:13 UTC
I am also experiencing this in approximately every 1 in 3 starts. The solution has been to kill the wpa_supplicant process and then restart the networkmanager daemon and then it will work until every other reboot.

I have included my daemon.log to analysis.
Comment 5 Gavin Graham 2007-09-19 02:03:05 UTC
Created attachment 95826 [details]
daemon.log output showing wpa_supplicant failure

This error is still happening. I have included the relevant portion of the daemon.log file to show that it is the wpa_supplicant process that is failing.
Comment 6 TJ 2007-09-20 10:19:02 UTC
Confirming with 0.6.5-0ubuntu11. Been using the work-around of restarting for a week or so now.


<info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting... 
<info>  Activation (eth1/wireless): access point 'tjworld.net' is encrypted, and a key exists.  No new key needed. 
<info>  supplicant_interface_init() - connect to global ctrl socket (0/10). 
SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant3^I' 
<info>  SUP: response was 'FAIL' 
<WARN>  nm_utils_supplicant_request_with_check(): supplicant_interface_init: supplicant error for 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant3^I'.  Response: 'FAIL' 
<WARN>  real_act_stage2_config(): Activation (eth1/wireless): couldn't connect to the supplicant. 
<info>  Activation (eth1) failure scheduled... 
<info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete. 
<info>  Activation (eth1) failed for access point (tjworld.net) 
<info>  Activation (eth1) failed. 
<info>  Deactivating device eth1. 
<WARN>  nm_signal_handler(): Caught signal 11.  Generating backtrace... 
******************* START **********************************
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
last message repeated 13 times
[Thread debugging using libthread_db enabled]
[New Thread 47936532240704 (LWP 6923)]
[New Thread 1098918224 (LWP 6967)]
[New Thread 1090525520 (LWP 6930)]
[New Thread 1082132816 (LWP 6927)]
(no debugging symbols found)
last message repeated 2 times
0x00002b99177b2c7f in waitpid () from /lib/libpthread.so.0
******************* END **********************************
Comment 7 unggnu 2008-02-15 00:05:30 UTC
It seems to be fixed in Ubuntu Gutsy 7.10.
Closing ...