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 770577 - Wifi link changing fails with "Too many open files"
Wifi link changing fails with "Too many open files"
Status: RESOLVED DUPLICATE of bug 770456
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
1.4.x
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-08-29 20:27 UTC by Norbert Kiesel
Modified: 2016-09-08 11:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Norbert Kiesel 2016-08-29 20:27:28 UTC 
Aug 29 12:37:25 lt-nkiesel dbus[877]: [system] Reloaded configuration
Aug 29 12:37:27 lt-nkiesel wpa_supplicant[1029]: wlan0: Reject scan trigger since one is already pending
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.4961] device (wlan0): supplicant interface state: ready -> inactive
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5160] policy: auto-activating connection 'MSPA3'
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5166] device (wlan0): Activation: starting connection 'MSPA3' (cfdda3bd-3e8e-4220-b2a3-3068e2a80a07)
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5167] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <error> [1472499448.5187] platform-linux: do-change-link[3]: failure changing link: failure 23 (Too many open files in system)
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <warn>  [1472499448.5187] device (wlan0): set-hw-addr: failed to set-cloned MAC address to B8:EE:65:58:B3:19 (permanent) (unspecified)
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5190] device (wlan0): state change: prepare -> failed (reason 'none') [40 120 0]
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <warn>  [1472499448.5193] device (wlan0): Activation: failed for connection 'MSPA3'
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5608] device (wlan0): state change: failed -> disconnected (reason 'none') [120 30 0]
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <error> [1472499448.5638] platform-linux: do-change-link[3]: failure changing link: failure 23 (Too many open files in system)
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <warn>  [1472499448.5638] device (wlan0): set-hw-addr: failed to set MAC address to 02:44:2B:70:5A:02 (scanning) (unspecified)
Aug 29 12:37:28 lt-nkiesel wpa_supplicant[1029]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Aug 29 12:37:28 lt-nkiesel NetworkManager[12781]: <info>  [1472499448.5658] policy: auto-activating connection 'MSPA3'
Aug 29 12:37:28 lt-nkiesel kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Aug 29 12:37:28 lt-nkiesel org.gnome.Shell.desktop[1599]: Gjs-Message: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Aug 29 12:37:28 lt-nkiesel org.gnome.Shell.desktop[22407]: Gjs-Message: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Comment 1 Thomas Haller 2016-08-29 20:39:34 UTC 
hi.

This is the same issue as bug 770456.

What kernel module are you using? Is there something of interest in dmesg?
Comment 2 Thomas Haller 2016-09-08 11:43:19 UTC 
Closing as duplicate.

*** This bug has been marked as a duplicate of bug 770456 ***