Bugzilla – Bug 803389
wpa_supplicant loaded twice preventng wifi from working
Last modified: 2014-06-13 07:44:03 UTC
After poking around a lot in network configuration, i found that /var/log/messages was screaming at me connecting disconnecting etcetcetc This condition started after a recent zypper up (my wifi was working nice before upgrading) - versions below Disabling wifi in Networkmanager and killing the remaining wpa_supplicant reenable wifi makes things work. Here some facts: rpm -qf /usr/sbin/wpa_supplicant wpa_supplicant-1.1-1.1.x86_64 linux:/etc/NetworkManager # ps -aux |grep wpa root 3031 0.7 0.0 29652 1560 ? Ss 19:05 0:05 wpa_supplicant -iwlan0 -c/var/run/wpa_supplicant-wlan0.conf -Dnl80211,wext -P/var/run/wpa_supplicant/wlan0.pid -B root 5382 0.8 0.0 29776 3108 ? S 19:07 0:05 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log root 6334 0.0 0.0 7056 860 pts/1 S+ 19:17 0:00 grep --color=auto wpa linux:/etc/NetworkManager # rpm -qa |grep Net NetworkManager-vpnc-0.9.6.0-2.1.x86_64 NetworkManager-pptp-kde4-0.9.0.7-1.1.x86_64 perl-Net-DBus-1.0.0-4.7.x86_64 NetworkManager-vpnc-kde4-0.9.0.7-1.1.x86_64 perl-NetxAP-0.02-715.4.x86_64 NetworkManager-openvpn-0.9.6.0-1.2.x86_64 NetworkManager-openvpn-kde4-0.9.0.7-1.1.x86_64 NetworkManager-0.9.6.4-7.1.x86_64 NetworkManager-kde4-libs-0.9.0.7-1.1.x86_64 NetworkManager-pptp-0.9.6.0-1.2.x86_64 NetworkManager-kde4-libs-lang-0.9.0.7-1.1.noarch
same for me: wifi does not work anymore after upate 12.2 -> 12.3-RC1 (tries to reconnect over and over again) $ ps uax | grep wpa root 1786 0.1 0.0 29648 2744 ? S 01:08 0:05 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log root 3345 0.2 0.0 29644 1492 ? Ss 01:09 0:07 wpa_supplicant -iwlan0 -c/var/run/wpa_supplicant-wlan0.conf -Dnl80211,wext -P/var/run/wpa_supplicant/wlan0.pid -B after "pkill wpa_supplicant" only one new wpa_supplicantis running and wifi works....
here is how i came out the misery: i removed /etc/systemd/system/multi-user.target.wants/NetworkManager.service and something like (sorry the lack of exactness, but i am on another machine) systemctl enable NetworkManager.service then things were good. On a sidenote, when typeing this, i see quite some broken link in the structure here on this machine - also an update. /etc/systemd/system/multi-user.target.wants # ll total 0 lrwxrwxrwx 1 root root 33 Apr 5 2012 acpid.service -> /lib/systemd/system/acpid.service lrwxrwxrwx 1 root root 40 May 31 2012 avahi-daemon.service -> /lib/systemd/system/avahi-daemon.service lrwxrwxrwx 1 root root 32 Apr 5 2012 cron.service -> /lib/systemd/system/cron.service lrwxrwxrwx 1 root root 37 May 31 2012 haveged.service -> ///lib/systemd/system/haveged.service lrwxrwxrwx 1 root root 46 Nov 19 13:30 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service lrwxrwxrwx 1 root root 33 Nov 19 15:11 nginx.service -> /lib/systemd/system/nginx.service lrwxrwxrwx 1 root root 35 Apr 5 2012 postfix.service -> /lib/systemd/system/postfix.service lrwxrwxrwx 1 root root 40 Dec 3 10:27 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target lrwxrwxrwx 1 root root 34 May 31 2012 sshd.service -> ///lib/systemd/system/sshd.service lrwxrwxrwx 1 root root 41 Jan 16 17:18 syslog-ng.service -> /usr/lib/systemd/system/syslog-ng.service only lrwxrwxrwx 1 root root 46 Nov 19 13:30 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service lrwxrwxrwx 1 root root 35 Apr 5 2012 postfix.service -> /lib/systemd/system/postfix.service lrwxrwxrwx 1 root root 40 Dec 3 10:27 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target lrwxrwxrwx 1 root root 41 Jan 16 17:18 syslog-ng.service -> /usr/lib/systemd/system/syslog-ng.service are NOT broken (the otheres are in red and indeed he files referred to does not exist)
I'd propose to find an isolate the problem. Would it be possible to disable Network Manager, configure the wifi in Yast and test ifup/ifdown. It would be good to find out if the problem is NetworkManager, systemd, or other component. Let's decide then if the Assignee shall be the maintainer of NM, systemd, or other. # systemctl disable NetworkManager.service
Closing.