|
On Sunday 12 May 2013 06:05:45 Cliff McDiarmid wrote: >> ----- Original Message ----- >> From: Lamarque V. Souza >> Sent: 05/11/13 04:53 PM >> To: networkmanager-list gnome org >> Subject: Re: NM not connecting with KDE4.10.2 >> >> On Saturday 11 May 2013 06:16:05 Cliff McDiarmid wrote: >> >Hi >> > >> >I have just installed NM-0.9.8.0 and wpa-supplicant-2.0 under KDE 4.10.2. >> > >> > D-bus is working fine, but after the intial: >> >May 9 22:52:04 cliffhanger NetworkManager[1895]: <info> NetworkManager >> >(version 0.9.8.0) is starting... May 9 22:52:04 cliffhanger >> >NetworkManager[1895]: <info> Read config file >> >/etc/NetworkManager/NetworkManager.conf May 9 22:52:04 cliffhanger >> >NetworkManager[1895]: <info> WEXT support is enabled May 9 22:52:05 >> >cliffhanger dbus[1872]: [system] Activating service >> >name='org.freedesktop.PolicyKit1' (using servicehelper) May 9 22:52:05 >> >cliffhanger polkitd[1930]: Started polkitd version 0.107 May 9 22:52:05 >> >cliffhanger dbus[1872]: [system] Successfully activated service >> >'org.freedesktop.PolicyKit1' May 9 22:52:05 cliffhanger >> >NetworkManager[1895]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red >> >Hat, >> >Inc. To report bugs please use the NetworkManager mailing list. May 9 >> >22:52:05 cliffhanger NetworkManager[1895]: <info> monitoring kernel >> >> firmware >> >> >directory '/lib/firmware'. May 9 22:52:05 cliffhanger >> >NetworkManager[1895]: >> ><info> rfkill0: found WiFi radio killswitch (at >> >/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill0) >> >(driver iwlwifi) May 9 22:52:05 cliffhanger NetworkManager[1895]: <info> >> >WiFi hardware radio set enabled May 9 22:52:05 cliffhanger dbus[1872]: >> >[system] Activating service name='org.bluez' (using servicehelper) May 9 >> >22:52:05 cliffhanger dbus[1872]: [system] Activated service 'org.bluez' >> >failed: Cannot launch daemon, file not found or permissions invalid May 9 >> >22:52:05 cliffhanger NetworkManager[1895]: <info> WiFi enabled by radio >> >killswitch; enabled by state file May 9 22:52:05 cliffhanger >> >NetworkManager[1895]: <info> WWAN enabled by radio killswitch; enabled by >> >state file May 9 22:52:05 cliffhanger NetworkManager[1895]: <info> WiMAX >> >enabled by radio killswitch; enabled by state file May 9 22:52:05 >> >cliffhanger NetworkManager[1895]: <info> Networking is enabled by state >> >file >> >May 9 22:52:05 cliffhanger NetworkManager[1895]: <info> (wlan0): using >> >nl80211 for WiFi device control May 9 22:52:05 cliffhanger >> >NetworkManager[1895]: <info> (wlan0): new 802.11 WiFi device (driver: >> >'iwlwifi' ifindex: 5) May 9 22:52:05 cliffhanger NetworkManager[1895]: >> ><info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0 May >> >> 9 >> >> >22:52:05 cliffhanger NetworkManager[1895]: <info> (wlan0): device state >> >change: unmanaged -> unavailable (reason 'managed') [10 20 2] May 9 >> >22:52:05 cliffhanger NetworkManager[1895]: <info> (wlan0): bringing up >> >device. May 9 22:52:06 cliffhanger NetworkManager[1895]: <info> (wlan0): >> >preparing device. May 9 22:52:06 cliffhanger NetworkManager[1895]: <info> >> >(wlan0): deactivating device (reason 'managed') [2] May 9 22:52:06 >> >cliffhanger dbus[1872]: [system] Activating service >> >name='fi.w1.wpa_supplicant1' (using servicehelper) May 9 22:52:06 >> >cliffhanger NetworkManager[1895]: <warn> failed to allocate link cache: >> >(-10) Operation not supported May 9 22:52:06 cliffhanger >> >NetworkManager[1895]: <info> (eth0): carrier is OFF May 9 22:52:06 >> >cliffhanger NetworkManager[1895]: <info> (eth0): new Ethernet device >> >(driver: 'sky2' ifindex: 3) May 9 22:52:06 cliffhanger >> >NetworkManager[1895]: <info> (eth0): exported as >> >/org/freedesktop/NetworkManager/Devices/1 May 9 22:52:06 cliffhanger >> >NetworkManager[1895]: <info> (eth0): device state change: unmanaged -> >> >unavailable (reason 'managed') [10 20 2] May 9 22:52:06 cliffhanger >> >NetworkManager[1895]: <info> (eth0): bringing up device. May 9 22:52:06 >> >cliffhanger NetworkManager[1895]: <info> (eth0): preparing device. May 9 >> >22:52:06 cliffhanger NetworkManager[1895]: <info> (eth0): deactivating >> >device (reason 'managed') [2] May 9 22:52:06 cliffhanger >> >NetworkManager[1895]: <info> Added default wired connection 'Wired >> >connection 1' for >> >/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/net/eth0 >> >May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/dummy0: couldn't determine device driver; >> >ignoring... May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... >> >May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/sit0: couldn't determine device driver; >> >ignoring... >> >May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/dummy0: couldn't determine device driver; >> >ignoring... May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... >> >May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> >> >/sys/devices/virtual/net/sit0: couldn't determine device driver; >> >ignoring... >> >May 9 22:52:06 cliffhanger NetworkManager[1895]: <warn> bluez error >> >> getting >> >> >default adapter: Cannot launch daemon, file not found or permissions >> >invalid >> > >> > >> >I'm getting the following error repeated agian and again: >> > >> >May 9 22:52:06 cliffhanger dbus[1872]: [system] Activated service >> >'fi.w1.wpa_supplicant1' failed: Launch helper exited with unknown return >> >code 255 May 9 22:52:06 cliffhanger NetworkManager[1895]: <error> >> >[1368136326.306764] [nm-supplicant-interface.c:997] interface_add_cb(): >> >(wlan0): error adding interface: Launch helper exited with unknown return >> >code 255 May 9 22:52:06 cliffhanger NetworkManager[1895]: >> >dbus_g_proxy_cancel_call: assertion `pending != NULL' failed May 9 >> >22:52:06 >> >cliffhanger NetworkManager[1895]: <info> (wlan0): supplicant interface >> >state: starting -> down May 9 22:52:06 cliffhanger NetworkManager[1895]: >> ><warn> Trying to remove a non-existant call id. May 9 22:52:06 cliffhanger >> >dbus[1872]: [system] Activating service name='fi.w1.wpa_supplicant1' >> >(using >> >servicehelper) >> >> Maybe the Excec= line in >> /etc/dbus-1/system.d/wpa_supplicant.conf is incorrect. Where did you >> install >> wpa_supplicant (the prefix you used)? > >Wpa_supplicant is installed to /sbin. >Files: > >[D-BUS Service] >Name=fi.epitest.hostap.WPASupplicant >Exec=/sbin/wpa_supplicant -u >User=root >SystemdService=wpa_supplicant.service > >[D-BUS Service] >Name=fi.w1.wpa_supplicant1 >Exec=/sbin/wpa_supplicant -u >User=root >SystemdService=wpa_supplicant.service
Looks correct.
>> >Under KDE the applet is saying that NM is not running and should be >> >started. >> > >> > Starting it manually has no effect. >> >> That message appear if the KDE applet (Plasma NM) is not able to >> contact NetworkManager, that usually happens when NM is not running but >> polkit or dbus problems can prevent Plasma NM from contacting NM. Is NM >> really >> >> running? What does the command 'ps u -C NetworkManager' return? > >USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
NM is not running. Can you run it in the command line as root with the command below and send me the file log.txt?
NetworkManager --no-daemon --log-level=DEBUG 2>&1 | tee log.txt
>> Did you compile both (or either) NM and wpa_supplicant yourself? > >Yes. NM with the following options: > >./configure --prefix=/usr \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --libexecdir=/usr/lib/NetworkManager \ > --disable-ppp
That seems ok too.
>And WPA with: > >CONFIG_BACKEND=file >CONFIG_CTRL_IFACE=y >CONFIG_DEBUG_FILE=y >CONFIG_DEBUG_SYSLOG=y >CONFIG_DEBUG_SYSLOG_FACILITY=LOG_DAEMON >CONFIG_DRIVER_NL80211=y >CONFIG_DRIVER_WEXT=y >CONFIG_DRIVER_WIRED=y >CONFIG_EAP_GTC=y >CONFIG_EAP_LEAP=y >CONFIG_EAP_MD5=y >CONFIG_EAP_MSCHAPV2=y >CONFIG_EAP_OTP=y >CONFIG_EAP_PEAP=y >CONFIG_EAP_TLS=y >CONFIG_EAP_TTLS=y >CONFIG_IEEE8021X_EAPOL=y >CONFIG_IPV6=y >CONFIG_LIBNL32=y >CONFIG_PEERKEY=y >CONFIG_PKCS12=y >CONFIG_READLINE=y >CONFIG_SMARTCARD=y >CONFIG_WPS=y >CFLAGS += -I/usr/include/libnl3 >CONFIG_CTRL_IFACE_DBUS=y >CONFIG_CTRL_IFACE_DBUS_NEW=y >CONFIG_CTRL_IFACE_DBUS_INTRO=y > >Can you tell me. How does NM know where to find the >'wpa_supplicant-wlan0.conf' file?
What is that file for? NM talks to wpa_supplicant through dbus when activating wifi connections, you should not need any extra wpa_supplicant configuration file. By the way, do you start wpa_supplicant using any script in /etc/init.d or something like that? NM starts wpa_supplicant, if there is another instance of wpa_supplicant running that can cause a conflict.
>Not only has its name been changed, but it now resides under /etc/sysconfig >and not in /etc.
No idea about that.
>many thanks > >MAC -- Lamarque V. Souza KDE's Network Management maintainer http://planetkde.org/pt-br |