310564 – Reconnection of disconnected wireless connection fails whether automatic or manual

Bug 310564 - Reconnection of disconnected wireless connection fails whether automatic or manual

Summary: Reconnection of disconnected wireless connection fails whether automatic or m...

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	Network Management
Classification:	Miscellaneous
Component:	Wireless (show other bugs)
Version:	unspecified
Platform:	Fedora RPMs Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	Lamarque V. Souza

URL:
Keywords:

Depends on:
Blocks:

Reported:	2012-11-23 17:49 UTC by ceolesen
Modified:	2012-12-01 21:57 UTC (History)
CC List:	0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description ceolesen 2012-11-23 17:49:00 UTC

The wireless connection between computer and mobile phone (as wifi hotspot) configured for automatic connection fails to reconnect automatically after a) the wireless signal temporarily drops, b) moving the mobile phone out of range and back in range or c) toggling enable of tethering on the mobile phone or manually by d) clickings to toggle the connection in the networkmanager widget in the tray.

The only workaround that I know of to reestablish the wireless connection aside from reboot of the computer is to toggle the checkmark reenabling wireless in the left side of the networkmanager widget in the tray followed by click on the connection in the right side.

Reproducible: Always

Steps to Reproduce:
The following is after the wireless connection is established say as a result of reboot of the computer with the connection configured for automatic connection.
1. Click on the wireless connection in the right side of the networkmanager widget in the tray to break the wireless connection. Observe the interface in the left side transitioning to "not connected".
2. Again click on the wireless connection but now to establish the connection. Observe the state change to "configuring interface", "waiting for authorization" and "not connected".
Actual Results:
The wireless connection is not reestablished

Expected Results:
The wireless connection should get reestablished

A workaround to reestablish the wireless connection after breaking the connection using the above Step 1 is
1. Toggle the checkmark reenabling the wireless option in the left side of the networkmanager widget in the tray.
2. Click the connection in the right side. Observe the interface transitioning to "connected to ...".

Distro is fully updated. Versions are
fedora 17
kernel 3.6.7-4.fc17.i686.PAE
kde 4.9.3

Comment 1 Lamarque V. Souza 2012-11-23 18:12:43 UTC

Which Plasma NM version do you use? You can see the version string in "Manage Connections"  -> "Other".

Is the "system connection" checkbox marked for you connection in the edit connection dialog?

I am assuming you use systemd, there are some problems between systemd and the secret agent implemented in Plasma NM. Marking your connection as system connection may help workaround those problems.

Also send me the NetworkManager log so that I can see why NetworkManager is not activating the connection. The auto-connect (and auto-reconnect) part is totally handled by NetworkManager daemon itself, the only thing Plasma NM does is save the configuration.

Comment 2 ceolesen 2012-11-23 19:47:05 UTC

(In reply to comment #1)
> Which Plasma NM version do you use? You can see the version string in
> "Manage Connections"  -> "Other".
Version 0.9.0.5 (nm09 20120930)

> Is the "system connection" checkbox marked for you connection in the edit
> connection dialog?
No. I tried again after marking it and a reboot but it made no difference.
 
> I am assuming you use systemd, there are some problems between systemd and
> the secret agent implemented in Plasma NM. Marking your connection as system
> connection may help workaround those problems.
> 
> Also send me the NetworkManager log so that I can see why NetworkManager is
> not activating the connection. The auto-connect (and auto-reconnect) part is
> totally handled by NetworkManager daemon itself, the only thing Plasma NM
> does is save the configuration.

I did not find a specific nm log.
The following is an extract from /var/log/messages after a reboot with reestablish of the connection from clicking the interface to disable the connection until reconnect by clicking the connection has failed and transitioned to "not connected"

Nov 23 20:21:26 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
Nov 23 20:21:26 xxxxxx NetworkManager[759]: <info> (wlan0): deactivating device (reason 'user-requested') [39]
Nov 23 20:21:26 xxxxxx NetworkManager[759]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1421
Nov 23 20:21:26 xxxxxx kernel: [  285.416531] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:21:26 xxxxxx avahi-daemon[765]: Withdrawing address record for 192.168.43.160 on wlan0.
Nov 23 20:21:26 xxxxxx avahi-daemon[765]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.160.
Nov 23 20:21:26 xxxxxx avahi-daemon[765]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 23 20:21:27 xxxxxx kernel: [  285.446079] cfg80211: Calling CRDA to update world regulatory domain
Nov 23 20:21:27 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: completed -> disconnected
Nov 23 20:21:27 xxxxxx kernel: [  285.454578] cfg80211: World regulatory domain updated:
Nov 23 20:21:27 xxxxxx kernel: [  285.454583] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:21:27 xxxxxx kernel: [  285.454585] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.454587] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.454588] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.454590] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.454592] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.454605] cfg80211: Calling CRDA for country: DK
Nov 23 20:21:27 xxxxxx kernel: [  285.457769] cfg80211: Regulatory domain changed to country: DK
Nov 23 20:21:27 xxxxxx kernel: [  285.457773] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:21:27 xxxxxx kernel: [  285.457775] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.457776] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.457778] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:21:27 xxxxxx kernel: [  285.457779] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Nov 23 20:21:27 xxxxxx dbus-daemon[778]: dbus[778]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 20:21:27 xxxxxx dbus[778]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 20:21:27 xxxxxx dbus-daemon[778]: dbus[778]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 20:21:27 xxxxxx dbus[778]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) starting connection 'Qa31klD9'
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0/wireless): access point 'Qa31klD9' has security, but secrets are required.
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Nov 23 20:22:03 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0/wireless): connection 'Qa31klD9' has security, and secrets exist.  No new secrets needed.
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: added 'ssid' value 'Qa31klD9'
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: added 'scan_ssid' value '1'
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: added 'psk' value '<omitted>'
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: added 'proto' value 'WPA RSN'
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> Config: set interface ap_scan to 1
Nov 23 20:22:04 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 23 20:22:06 xxxxxx kernel: [  325.401819] wlan0: authenticate with 50:cc:f8:bc:78:2b
Nov 23 20:22:06 xxxxxx kernel: [  325.409867] wlan0: send auth to 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 20:22:06 xxxxxx kernel: [  325.411730] wlan0: authenticated
Nov 23 20:22:06 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 23 20:22:06 xxxxxx kernel: [  325.414033] wlan0: associate with 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 20:22:06 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 23 20:22:06 xxxxxx kernel: [  325.418939] wlan0: RX AssocResp from 50:cc:f8:bc:78:2b (capab=0x411 status=0 aid=1)
Nov 23 20:22:06 xxxxxx kernel: [  325.420498] wlan0: associated
Nov 23 20:22:06 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 23 20:22:16 xxxxxx kernel: [  335.422247] wlan0: disassociating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:16 xxxxxx kernel: [  335.433163] cfg80211: Calling CRDA to update world regulatory domain
Nov 23 20:22:16 xxxxxx kernel: [  335.433870] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:16 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associated -> disconnected
Nov 23 20:22:16 xxxxxx kernel: [  335.442322] cfg80211: World regulatory domain updated:
Nov 23 20:22:16 xxxxxx kernel: [  335.442331] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:22:16 xxxxxx kernel: [  335.442337] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:16 xxxxxx kernel: [  335.442342] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:16 xxxxxx kernel: [  335.442347] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:16 xxxxxx kernel: [  335.442352] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:16 xxxxxx kernel: [  335.442357] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:16 xxxxxx kernel: [  335.442390] cfg80211: Calling CRDA for country: DK
Nov 23 20:22:17 xxxxxx kernel: [  335.447420] cfg80211: Regulatory domain changed to country: DK
Nov 23 20:22:17 xxxxxx kernel: [  335.447427] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:22:17 xxxxxx kernel: [  335.447433] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:17 xxxxxx kernel: [  335.447437] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:17 xxxxxx kernel: [  335.447442] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:17 xxxxxx kernel: [  335.447446] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Nov 23 20:22:17 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 23 20:22:20 xxxxxx kernel: [  339.180073] wlan0: authenticate with 50:cc:f8:bc:78:2b
Nov 23 20:22:20 xxxxxx kernel: [  339.184961] wlan0: send auth to 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 20:22:20 xxxxxx kernel: [  339.186915] wlan0: authenticated
Nov 23 20:22:20 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 23 20:22:20 xxxxxx kernel: [  339.192023] wlan0: associate with 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 20:22:20 xxxxxx kernel: [  339.196822] wlan0: RX AssocResp from 50:cc:f8:bc:78:2b (capab=0x411 status=0 aid=1)
Nov 23 20:22:20 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 23 20:22:20 xxxxxx kernel: [  339.201139] wlan0: associated
Nov 23 20:22:20 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 23 20:22:27 xxxxxx systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Nov 23 20:22:27 xxxxxx chronyd[788]: Source 85.82.15.46 offline
Nov 23 20:22:27 xxxxxx chronyd[788]: Source 77.233.251.107 offline
Nov 23 20:22:27 xxxxxx chronyd[788]: Source 87.48.12.24 offline
Nov 23 20:22:27 xxxxxx chronyd[788]: Source 217.198.219.102 offline
Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): association took too long.
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): asking for new secrets
Nov 23 20:22:29 xxxxxx kernel: [  348.017451] cfg80211: Calling CRDA to update world regulatory domain
Nov 23 20:22:29 xxxxxx kernel: [  348.021459] cfg80211: World regulatory domain updated:
Nov 23 20:22:29 xxxxxx kernel: [  348.021462] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:22:29 xxxxxx kernel: [  348.021464] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.021466] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.021468] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.021469] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.021471] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.021482] cfg80211: Calling CRDA for country: DK
Nov 23 20:22:29 xxxxxx kernel: [  348.025147] cfg80211: Regulatory domain changed to country: DK
Nov 23 20:22:29 xxxxxx kernel: [  348.025150] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 20:22:29 xxxxxx kernel: [  348.025152] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.025154] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.025156] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 20:22:29 xxxxxx kernel: [  348.025157] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associated -> disconnected
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <warn> No agents were available for this request.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> Marking connection 'Qa31klD9' invalid.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0) failed for connection 'Qa31klD9'
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> (wlan0): deactivating device (reason 'none') [0]
Nov 23 20:25:12 xxxxxx dbus-daemon[778]: dbus[778]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 23 20:25:12 xxxxxx dbus[778]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 23 20:25:12 xxxxxx dbus-daemon[778]: dbus[778]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 23 20:25:12 xxxxxx dbus[778]: [system] Successfully activated service 'org.freedesktop.PackageKit'

Comment 3 ceolesen 2012-11-23 20:31:47 UTC

in case useful the following is the same type of extract as under comment #1 but with the difference that the reconnect is successful and automatic following a toggle of the check mark for the wireless option in the left side of the nm widget instead of clicking the interface off and the connection on as under comment #1

Nov 23 21:15:04 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: activated -> unavailable (reason 'none') [100 20 0]
Nov 23 21:15:04 xxxxxx NetworkManager[771]: <info> (wlan0): deactivating device (reason 'none') [0]
Nov 23 21:15:05 xxxxxx NetworkManager[771]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1283
Nov 23 21:15:05 xxxxxx kernel: [  242.842666] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 21:15:05 xxxxxx kernel: [  242.881440] cfg80211: Calling CRDA to update world regulatory domain
Nov 23 21:15:05 xxxxxx avahi-daemon[788]: Withdrawing address record for 192.168.43.160 on wlan0.
Nov 23 21:15:05 xxxxxx avahi-daemon[788]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.160.
Nov 23 21:15:05 xxxxxx avahi-daemon[788]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 23 21:15:05 xxxxxx NetworkManager[771]: <info> (wlan0): taking down device.
Nov 23 21:15:05 xxxxxx kernel: [  242.904078] cfg80211: World regulatory domain updated:
Nov 23 21:15:05 xxxxxx kernel: [  242.904083] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 21:15:05 xxxxxx kernel: [  242.904085] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.904087] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.904089] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.904090] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.904092] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.904103] cfg80211: Calling CRDA for country: DK
Nov 23 21:15:05 xxxxxx dbus-daemon[819]: dbus[819]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 21:15:05 xxxxxx kernel: [  242.909086] cfg80211: Regulatory domain changed to country: DK
Nov 23 21:15:05 xxxxxx kernel: [  242.909091] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 23 21:15:05 xxxxxx kernel: [  242.909093] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.909094] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.909096] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 23 21:15:05 xxxxxx kernel: [  242.909097] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Nov 23 21:15:05 xxxxxx dbus[819]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 21:15:05 xxxxxx avahi-daemon[788]: Withdrawing address record for fe80::222:fbff:fe2e:a1a2 on wlan0.
Nov 23 21:15:05 xxxxxx NetworkManager[771]: <info> WiFi hardware radio set disabled
Nov 23 21:15:05 xxxxxx NetworkManager[771]: <info> WiFi now disabled by radio killswitch
Nov 23 21:15:05 xxxxxx dbus-daemon[819]: dbus[819]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 21:15:05 xxxxxx dbus[819]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 21:15:05 xxxxxx chronyd[810]: Source 217.116.227.3 offline
Nov 23 21:15:05 xxxxxx chronyd[810]: Source 193.162.159.97 offline
Nov 23 21:15:05 xxxxxx chronyd[810]: Source 87.104.211.8 offline
Nov 23 21:15:05 xxxxxx chronyd[810]: Source 85.82.15.46 offline
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0): bringing up device.
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> WiFi hardware radio set enabled
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> WiFi now enabled by radio killswitch
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0): bringing up device.
Nov 23 21:15:44 xxxxxx kernel: [  282.442817] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
Nov 23 21:15:44 xxxxxx kernel: [  282.447213] iwlwifi 0000:04:00.0: Radio type=0x1-0x2-0x0
Nov 23 21:15:44 xxxxxx kernel: [  282.489567] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0) supports 5 scan SSIDs
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <warn> Trying to remove a non-existant call id.
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: ready -> inactive
Nov 23 21:15:44 xxxxxx NetworkManager[771]: <info> (wlan0) supports 5 scan SSIDs
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Auto-activating connection 'Qa31klD9'.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) starting connection 'Qa31klD9'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0/wireless): access point 'Qa31klD9' has security, but secrets are required.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0/wireless): connection 'Qa31klD9' has security, and secrets exist.  No new secrets needed.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: added 'ssid' value 'Qa31klD9'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: added 'scan_ssid' value '1'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: added 'psk' value '<omitted>'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: added 'proto' value 'WPA RSN'
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> Config: set interface ap_scan to 1
Nov 23 21:15:47 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: inactive -> scanning
Nov 23 21:15:50 xxxxxx kernel: [  288.518767] wlan0: authenticate with 50:cc:f8:bc:78:2b
Nov 23 21:15:50 xxxxxx kernel: [  288.524713] wlan0: send auth to 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 21:15:50 xxxxxx kernel: [  288.526602] wlan0: authenticated
Nov 23 21:15:50 xxxxxx kernel: [  288.527063] wlan0: associate with 50:cc:f8:bc:78:2b (try 1/3)
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 23 21:15:50 xxxxxx kernel: [  288.537451] wlan0: RX AssocResp from 50:cc:f8:bc:78:2b (capab=0x411 status=0 aid=1)
Nov 23 21:15:50 xxxxxx kernel: [  288.542522] wlan0: associated
Nov 23 21:15:50 xxxxxx kernel: [  288.542555] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Qa31klD9'.
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> dhclient started with pid 1749
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Nov 23 21:15:50 xxxxxx dhclient[1749]: Internet Systems Consortium DHCP Client 4.2.4-P2
Nov 23 21:15:50 xxxxxx dhclient[1749]: Copyright 2004-2012 Internet Systems Consortium.
Nov 23 21:15:50 xxxxxx dhclient[1749]: All rights reserved.
Nov 23 21:15:50 xxxxxx dhclient[1749]: For info, please visit https://www.isc.org/software/dhcp/
Nov 23 21:15:50 xxxxxx dhclient[1749]: 
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Nov 23 21:15:50 xxxxxx dhclient[1749]: Listening on LPF/wlan0/00:22:fb:2e:a1:a2
Nov 23 21:15:50 xxxxxx dhclient[1749]: Sending on   LPF/wlan0/00:22:fb:2e:a1:a2
Nov 23 21:15:50 xxxxxx dhclient[1749]: Sending on   Socket/fallback
Nov 23 21:15:50 xxxxxx dhclient[1749]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 (xid=0x4aef060)
Nov 23 21:15:50 xxxxxx dhclient[1749]: DHCPACK from 192.168.43.1 (xid=0x4aef060)
Nov 23 21:15:50 xxxxxx dhclient[1749]: bound to 192.168.43.160 -- renewal in 1776 seconds.
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info>   address 192.168.43.160
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info>   prefix 24 (255.255.255.0)
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info>   gateway 192.168.43.1
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info>   hostname 'xxxxxx'
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info>   nameserver '192.168.43.1'
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 23 21:15:50 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov 23 21:15:50 xxxxxx avahi-daemon[788]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.160.
Nov 23 21:15:50 xxxxxx avahi-daemon[788]: New relevant interface wlan0.IPv4 for mDNS.
Nov 23 21:15:50 xxxxxx avahi-daemon[788]: Registering new address record for 192.168.43.160 on wlan0.IPv4.
Nov 23 21:15:51 xxxxxx NetworkManager[771]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Nov 23 21:15:51 xxxxxx avahi-daemon[788]: Registering new address record for fe80::222:fbff:fe2e:a1a2 on wlan0.*.
Nov 23 21:15:51 xxxxxx NetworkManager[771]: <info> Policy set 'Qa31klD9' (wlan0) as default for IPv4 routing and DNS.
Nov 23 21:15:51 xxxxxx NetworkManager[771]: <info> Activation (wlan0) successful, device activated.
Nov 23 21:15:51 xxxxxx dbus-daemon[819]: dbus[819]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 21:15:51 xxxxxx dbus[819]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 23 21:15:51 xxxxxx NetworkManager[771]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 23 21:15:51 xxxxxx dbus-daemon[819]: dbus[819]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 21:15:51 xxxxxx dbus[819]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 23 21:15:52 xxxxxx chronyd[810]: Source 85.82.15.46 online
Nov 23 21:15:52 xxxxxx chronyd[810]: Source 217.116.227.3 online
Nov 23 21:15:52 xxxxxx chronyd[810]: Source 193.162.159.97 online
Nov 23 21:15:52 xxxxxx chronyd[810]: Source 87.104.211.8 online
Nov 23 21:15:52 xxxxxx dbus-daemon[819]: Redirecting to /bin/systemctl reload  squid.service

Comment 4 Lamarque V. Souza 2012-11-25 21:10:19 UTC

Nov 23 20:22:06 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 23 20:22:16 xxxxxx kernel: [  335.422247] wlan0: disassociating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:16 xxxxxx kernel: [  335.433163] cfg80211: Calling CRDA to update world regulatory domain
Nov 23 20:22:16 xxxxxx kernel: [  335.433870] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:16 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associated -> disconnected

the wifi driver is disassociating from the access point here. This looks like a problem in your driver or in your network. Which wifi card do you use?

Comment 5 ceolesen 2012-11-26 19:10:21 UTC

(In reply to comment #4)
> Nov 23 20:22:06 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant
> interface state: associating -> associated
> Nov 23 20:22:16 xxxxxx kernel: [  335.422247] wlan0: disassociating from
> 50:cc:f8:bc:78:2b by local choice (reason=3)
> Nov 23 20:22:16 xxxxxx kernel: [  335.433163] cfg80211: Calling CRDA to
> update world regulatory domain
> Nov 23 20:22:16 xxxxxx kernel: [  335.433870] wlan0: deauthenticating from
> 50:cc:f8:bc:78:2b by local choice (reason=3)
> Nov 23 20:22:16 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant
> interface state: associated -> disconnected
> 
> the wifi driver is disassociating from the access point here. This looks
> like a problem in your driver or in your network. Which wifi card do you use?
extract from lshw:
           *-network
                description: Wireless interface
                product: WiFi Link 5100
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:04:00.0
                logical name: wlan0
                version: 00
                serial: 00:22:fb:2e:a1:a2
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=iwlwifi driverversion=3.6.7-4.fc17.i686.PAE firmware=8.83.5.1 build 33692 ip=192.168.43.156 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
                resources: irq:46 memory:f8000000-f8001fff

Still, if I break the wireless connection by clicking on the red dot with an x in it in the left side of the nm tray widget

and then attempt to reestablish the connection by clicking the connection in the right side then the connection fails

whereas if I in between click the checkmark box next to "Enable wireless" in the lower left corner twice for a toggle then the connection succeeds.

Comment 6 Lamarque V. Souza 2012-11-27 12:03:06 UTC

Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): association took too long.
Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): association took too long.
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): asking for new secrets

I also own an Intel wifi card and it has problems to work in a crowed environment, specially in a mixed 2.4 GHz and 5 GHz network. Maybe that is the cause of the associate error message above. It took 9 seconds between the begining of the associating and the failed messages, that's too short period in my opinion. That must be something wrong in the driver  or in wpa_supplicant you are using.


Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): supplicant interface state: associated -> disconnected
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <warn> No agents were available for this request.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <info> Marking connection 'Qa31klD9' invalid.
Nov 23 20:24:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0) failed for connection 'Qa31klD9'

For some reason NetworkManager is not able to contact the secret agent in Plasma NM, maybe this has something to do with logind. Logind does not do a good job in replacing ConsoleKit, it probably requires modification in Plasma NM but I cannot find any documentation about what should be changed. If the connection is marked as invalid (like above) then NetworkManager does not even try to activate it in the future.

Comment 7 ceolesen 2012-11-27 13:09:26 UTC

I dont know what to tell you except that it looks like the toggling of the checkmark for "enable wireless" includes "something" that makes the subsequent connect work such as when clicking the connection and that that "something" perhaps is what should be included in the disconnect such as when the interface is clicked for the subsequent connect to work such as when clicking the connection. Perhaps that "something" is a cleanup or reset of something.

Comment 8 Lamarque V. Souza 2012-11-27 18:05:11 UTC

(In reply to comment #7)
> I dont know what to tell you except that it looks like the toggling of the
> checkmark for "enable wireless" includes "something" that makes the
> subsequent connect work such as when clicking the connection and that that
> "something" perhaps is what should be included in the disconnect such as
> when the interface is clicked for the subsequent connect to work such as
> when clicking the connection. Perhaps that "something" is a cleanup or reset
> of something.

That is not what Plasma NM is meant to do according to the NetworkManager specification. Disabling and enabling wireless must be resetting the wifi card to the correct state, if so then this is a driver issue.

Comment 9 ceolesen 2012-11-27 18:57:54 UTC

In case I've now inadvertently confused the issue then here again are the 2
sequences I've been using to illustrate the problem:

precondition for both sequences: wireless connection is established

1. this sequence does not work but should
1a. click the red dot on the interface (in the left side) to disconnect.
expected result: state turns to not connected. observed result: same as
expected.
1b. click on the connection (in the right side) to connect. expected
result: state turns to connected. observed result: state turns to not
connected.

2. this sequence works
2a. same as 1a (but probably superfluous as also implied by 2b)
2b. toggle the checkmark off-on next to "enable wireless" (in the lower
left side)
2c. same as 1b except for the observed result: state turns to connected.

On Tue, Nov 27, 2012 at 7:05 PM, Lamarque V. Souza <lamarque@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=310564
>
> --- Comment #8 from Lamarque V. Souza <lamarque@kde.org> ---
> (In reply to comment #7)
> > I dont know what to tell you except that it looks like the toggling of
> the
> > checkmark for "enable wireless" includes "something" that makes the
> > subsequent connect work such as when clicking the connection and that
> that
> > "something" perhaps is what should be included in the disconnect such as
> > when the interface is clicked for the subsequent connect to work such as
> > when clicking the connection. Perhaps that "something" is a cleanup or
> reset
> > of something.
>
> That is not what Plasma NM is meant to do according to the NetworkManager
> specification. Disabling and enabling wireless must be resetting the wifi
> card
> to the correct state, if so then this is a driver issue.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

Comment 10 Lamarque V. Souza 2012-12-01 17:25:02 UTC

Again: this is not a issue in Plasma NM, it is probably a issue in the driver or in NetworkManager, there is nothing I can do about it.

By these lines:

Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from 50:cc:f8:bc:78:2b by local choice (reason=3)
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): association took too long.
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation (wlan0/wireless): asking for new secrets

When NetworkManager tries to deauthenticate something wrong is happening. The message "association took too long" should not appear here since this is a deactivation not activation of a connection. That part of the activation process is out of control of Plasma NM. You may be using a version of NetworkManager that is not that stable or it is really a driver issue.

Comment 11 ceolesen 2012-12-01 18:27:44 UTC

The distro I'm using is standard unmodified Fedora 17 fully up-to-date.

Are you the maintainer of the NM widget but only the widget and not also
the NM?

To test your theory - do you know the commandline commands to do the
equivalent from the commandline i.e. to disconnect and reconnect the
wireless connection?




On Sat, Dec 1, 2012 at 6:25 PM, Lamarque V. Souza <lamarque@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=310564
>
> --- Comment #10 from Lamarque V. Souza <lamarque@kde.org> ---
> Again: this is not a issue in Plasma NM, it is probably a issue in the
> driver
> or in NetworkManager, there is nothing I can do about it.
>
> By these lines:
>
> Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from
> 50:cc:f8:bc:78:2b by local choice (reason=3)
> Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> (wlan0/wireless):
> association took too long.
> Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state
> change: config -> need-auth (reason 'none') [50 60 0]
> Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> (wlan0/wireless):
> asking for new secrets
>
> When NetworkManager tries to deauthenticate something wrong is happening.
> The
> message "association took too long" should not appear here since this is a
> deactivation not activation of a connection. That part of the activation
> process is out of control of Plasma NM. You may be using a version of
> NetworkManager that is not that stable or it is really a driver issue.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

Comment 12 Lamarque V. Souza 2012-12-01 19:46:52 UTC

(In reply to comment #11)
> The distro I'm using is standard unmodified Fedora 17 fully up-to-date.


 
> Are you the maintainer of the NM widget but only the widget and not also
> the NM?

NetworkManager is developed by the RedHat guys, not KDE. 
 
> To test your theory - do you know the commandline commands to do the
> equivalent from the commandline i.e. to disconnect and reconnect the
> wireless connection?
> 
> 
> 
> 
> On Sat, Dec 1, 2012 at 6:25 PM, Lamarque V. Souza <lamarque@kde.org> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=310564
> >
> > --- Comment #10 from Lamarque V. Souza <lamarque@kde.org> ---
> > Again: this is not a issue in Plasma NM, it is probably a issue in the
> > driver
> > or in NetworkManager, there is nothing I can do about it.
> >
> > By these lines:
> >
> > Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from
> > 50:cc:f8:bc:78:2b by local choice (reason=3)
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> > (wlan0/wireless):
> > association took too long.
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state
> > change: config -> need-auth (reason 'none') [50 60 0]
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> > (wlan0/wireless):
> > asking for new secrets
> >
> > When NetworkManager tries to deauthenticate something wrong is happening.
> > The
> > message "association took too long" should not appear here since this is a
> > deactivation not activation of a connection. That part of the activation
> > process is out of control of Plasma NM. You may be using a version of
> > NetworkManager that is not that stable or it is really a driver issue.
> >
> > --
> > You are receiving this mail because:
> > You reported the bug.
> >

Comment 13 Lamarque V. Souza 2012-12-01 19:47:42 UTC

Sorry, pressed ENTER by accident.

(In reply to comment #11)
> The distro I'm using is standard unmodified Fedora 17 fully up-to-date.


 
> Are you the maintainer of the NM widget but only the widget and not also
> the NM?
> 
> To test your theory - do you know the commandline commands to do the
> equivalent from the commandline i.e. to disconnect and reconnect the
> wireless connection?
> 
> 
> 
> 
> On Sat, Dec 1, 2012 at 6:25 PM, Lamarque V. Souza <lamarque@kde.org> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=310564
> >
> > --- Comment #10 from Lamarque V. Souza <lamarque@kde.org> ---
> > Again: this is not a issue in Plasma NM, it is probably a issue in the
> > driver
> > or in NetworkManager, there is nothing I can do about it.
> >
> > By these lines:
> >
> > Nov 23 20:22:29 xxxxxx kernel: [  348.004173] wlan0: deauthenticating from
> > 50:cc:f8:bc:78:2b by local choice (reason=3)
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> > (wlan0/wireless):
> > association took too long.
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <info> (wlan0): device state
> > change: config -> need-auth (reason 'none') [50 60 0]
> > Nov 23 20:22:29 xxxxxx NetworkManager[759]: <warn> Activation
> > (wlan0/wireless):
> > asking for new secrets
> >
> > When NetworkManager tries to deauthenticate something wrong is happening.
> > The
> > message "association took too long" should not appear here since this is a
> > deactivation not activation of a connection. That part of the activation
> > process is out of control of Plasma NM. You may be using a version of
> > NetworkManager that is not that stable or it is really a driver issue.
> >
> > --
> > You are receiving this mail because:
> > You reported the bug.
> >

Comment 14 Lamarque V. Souza 2012-12-01 19:53:15 UTC

Sorry, pressed ENTER by accident.

(In reply to comment #11)
> The distro I'm using is standard unmodified Fedora 17 fully up-to-date.

I do not use Fedora, so I do not know which NetworkManager version is shipped with it.
 
> Are you the maintainer of the NM widget but only the widget and not also
> the NM?

Yes. KDE does not develop NetworkManager.
 
> To test your theory - do you know the commandline commands to do the
> equivalent from the commandline i.e. to disconnect and reconnect the
> wireless connection?

You can use the nmcli command (from NetworkManager package) to (de)activate connections:

nmcli con # to list all connections including their uuid's
nmcli con up uuid <uuid> # to activate the connection
nmcli con down uuid <uuid> # to deactivate the connection

Comment 15 ceolesen 2012-12-01 21:31:54 UTC

Thanks for the commands.
Using the commands instead of the mn widget made no difference i.e. does
not disagree with your theory that the culprit is not the nm widget.
Further, the commands are successful with the wifi spot provided by my wifi
router but again not with the wifi spot provided by my mobile phone.
I'll file the bug report with Fedora's bugzilla instead.
Thanks for your time.




On Sat, Dec 1, 2012 at 8:53 PM, Lamarque V. Souza <lamarque@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=310564
>
> --- Comment #14 from Lamarque V. Souza <lamarque@kde.org> ---
> Sorry, pressed ENTER by accident.
>
> (In reply to comment #11)
> > The distro I'm using is standard unmodified Fedora 17 fully up-to-date.
>
> I do not use Fedora, so I do not know which NetworkManager version is
> shipped
> with it.
>
> > Are you the maintainer of the NM widget but only the widget and not also
> > the NM?
>
> Yes. KDE does not develop NetworkManager.
>
> > To test your theory - do you know the commandline commands to do the
> > equivalent from the commandline i.e. to disconnect and reconnect the
> > wireless connection?
>
> You can use the nmcli command (from NetworkManager package) to (de)activate
> connections:
>
> nmcli con # to list all connections including their uuid's
> nmcli con up uuid <uuid> # to activate the connection
> nmcli con down uuid <uuid> # to deactivate the connection
>
> --
> You are receiving this mail because:
> You reported the bug.
>