You are not logged in.
On 4.0.1-1-ARCH, Desktop = KDE 4.14.7.
Since a recent update, I seem to have a wifi issue with random connections. I thought that was related to the following discussion: https://bbs.archlinux.org/viewtopic.php?id=196584
But the problem was not solved by the latest update of wpa_supplicant as supposed to be according to the trend.
I initially tried to review my connection setup manually and ended up with dhcpcd waiting for carrier until time was out. Then I tried automatic connection setup tools such as NetworkManager and eventually wicd.
With wicd, the symtom I get is just that: every first boot of the day fails and I just have to reboot to get a connection ! Maybe this is an obvious symptom of something but I can't find out. If this talks to you ...
Here is an extract of /var/log/wicd/wicd.log
2015/05/11 19:42:27 :: Generating psk...
2015/05/11 19:42:27 :: Attempting to authenticate...
2015/05/11 19:43:02 :: wpa_supplicant authentication may have failed.
2015/05/11 19:43:02 :: connect result is failed
2015/05/11 19:43:02 :: exiting connection thread
2015/05/11 19:43:07 :: Sending connection attempt result bad_pass
2015/05/11 19:43:07 :: Autoconnecting...
2015/05/11 19:43:07 :: No wired connection present, attempting to autoconnect to wireless network
2015/05/11 19:43:08 :: hidden
2015/05/11 19:43:08 :: MY_SSID has no never connect value
2015/05/11 19:43:08 :: trying to automatically connect to...MY_SSID
2015/05/11 19:43:08 :: Connecting to wireless network MY_SSID
2015/05/11 19:43:09 :: Putting interface down
2015/05/11 19:43:09 :: Releasing DHCP leases...
2015/05/11 19:43:09 :: Setting false IP...
2015/05/11 19:43:09 :: Stopping wpa_supplicant
2015/05/11 19:43:09 :: Flushing the routing table...
2015/05/11 19:43:09 :: Putting interface up...and after reboot :
2015/05/11 19:44:12 :: Attempting to authenticate...
2015/05/11 19:44:20 :: Running DHCP with NO hostname
2015/05/11 19:44:24 :: DUID 00:01:00:01:1a:92:ac:00:e8:39:df:3d:f5:54
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: IAID df:3d:f5:54
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: soliciting an IPv6 router
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: soliciting a DHCP lease
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: offered 192.168.1.52 from 192.168.1.1
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: leased 192.168.1.52 for 86400 seconds
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: adding route to 192.168.1.0/24
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: wlp2s0: adding default route via 192.168.1.1
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: forked to background, child pid 509
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 ::
2015/05/11 19:44:24 :: DHCP connection successful
2015/05/11 19:44:24 :: not verifying
2015/05/11 19:44:24 :: Connecting thread exiting.
2015/05/11 19:44:26 :: Sending connection attempt result successThis is what I used to have when using NetworkManager (journalctl --unit=NeworkManager)
mai 08 15:26:42 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
mai 08 15:26:43 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: scanning -> authenticating
mai 08 15:26:44 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: authenticating -> disconnected
mai 08 15:26:49 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
mai 08 15:26:56 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: scanning -> authenticating
mai 08 15:26:56 John_Difool NetworkManager[250]: <info> (wlp2s0): supplicant interface state: authenticating -> disconnected
mai 08 15:27:03 John_Difool NetworkManager[250]: <warn> (wlp2s0): Activation: (wifi) association took too long, failing activation
mai 08 15:27:03 John_Difool NetworkManager[250]: <info> (wlp2s0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
mai 08 15:27:03 John_Difool NetworkManager[250]: <info> NetworkManager state is now DISCONNECTEDand here is the kind of journald message I get with wpa_supplicant (launched by NetworkManagement)
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: SME: Trying to authenticate with 00:17:33:a0:34:ac (SSID='MY_SSID' freq=2462 MHz)
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=2 duration=20 reason=CONN_FAILED
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: SME: Trying to authenticate with 00:17:33:a0:34:ac (SSID='MY_SSID' freq=2462 MHz)
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=1 duration=10 reason=CONN_FAILED
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="MY_SSID"
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: SME: Trying to authenticate with 00:17:33:a0:34:ac (SSID='MY_SSID' freq=2462 MHz)
mai 08 15:24:09 John_Difool wpa_supplicant[274]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MY_SSID" auth_failures=2 duration=20 reason=CONN_FAILED
mai 08 15:24:09 John_Difool wpa_supplicant[274]: rfkill: WLAN soft blocked
mai 08 15:24:09 John_Difool wpa_supplicant[274]: rfkill: WLAN soft blockedOffline