Bug 18589

Summary: wireless will not connect after reboot(for new glibc) -- also fails after logout/login
Product: Mageia Reporter: Pierre Fortin <pf>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 5   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: networkmanager CVE:
Status comment:
Attachments: Modified diff of package changes since last reboot on April 9
/var/log/messages while trying to bring up WiFi

Description Pierre Fortin 2016-05-30 19:51:40 CEST
Description of problem:  Reboot needed for new glibc; after which wireless will not connect. Last reboot was April 9.  For a list of packages changed since last reboot, see https://bugs.mageia.org/attachment.cgi?id=7877 in bug 18588


Version-Release number of selected component (if applicable):


How reproducible: always. Problem survives reboot.  


Steps to Reproduce:
1. No idea what caused this. Simply rebooted after package updates.
2.
3.
Comment 1 Pierre Fortin 2016-05-30 19:52:50 CEST
Created attachment 7878 [details]
Modified diff of package changes since last reboot on April 9
Comment 2 Pierre Fortin 2016-05-30 19:56:53 CEST
Created attachment 7879 [details]
/var/log/messages while trying to bring up WiFi

Tried to bring up wireless:
1. with ethernet connected
2. without ethernet connected (just in case)
Comment 3 Pierre Fortin 2016-05-30 20:33:20 CEST
Found https://forums.mageia.org/en/viewtopic.php?f=25&t=5782

# sed -i 's/NM_CONTROLLED=no/NM_CONTROLLED=yes/' /etc/sysconfig/network-scripts/ifcfg-*
# systemctl enable NetworkManager.service
# systemctl stop NetworkManager.service
# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.101  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::eef4:bbff:fe0e:1168  prefixlen 64  scopeid 0x20<link>
        ether ec:f4:bb:0e:11:68  txqueuelen 1000  (Ethernet)
        RX packets 1686160  bytes 2498668173 (2.3 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 978703  bytes 74154649 (70.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7d00000-f7d20000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 278247  bytes 105667179 (100.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 278247  bytes 105667179 (100.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Wireless interface now not showing... 
Used mcc to configure wireless and got this on konsole:
# Ignore the following Glib::Object::Introspection & Gtk3 warnings
Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257.
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Failed to connect to non-global ctrl_ifname: (null)  error: Success
Failed to create host name resolver: Invalid host name
run-parts: /etc/sysconfig/network-scripts/hostname.d/avahi exited with return code 1
Ignore the following Glib::Object::Introspection & Gtk3 warnings
Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257.
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Failed to connect to non-global ctrl_ifname: (null)  error: Success
Failed to create host name resolver: Invalid host name
run-parts: /etc/sysconfig/network-scripts/hostname.d/avahi exited with return code 1
Failed to kill daemon. (No such file or directory)
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlp3s0 ; Invalid argument.
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument

However...
# ifconfig
eno1: [same as above]

lo: [same as above]

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.14  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::a2a8:cdff:fead:3b71  prefixlen 64  scopeid 0x20<link>
        ether a0:a8:cd:ad:3b:71  txqueuelen 1000  (Ethernet)
        RX packets 109  bytes 68217 (66.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 148  bytes 38512 (37.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and finally, WiFi is working again...

Leaving this bug new/open as this problem should not have occurred.  Network Manager was installed and it was only updated during the April 9 - May 29 session.
Comment 4 Pierre Fortin 2016-05-31 17:07:39 CEST
Rebooted & WiFi down again. 
Need:
   systemctl stop NetworkManager.service
   service network start 
Ok.. I'm still somewhat old-school... ;]
Comment 5 Marja Van Waes 2016-05-31 19:15:36 CEST
Assigning to NetworkManager, which unfortunately has no maintainer. So assigning to all packagers collectively.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs
Source RPM: (none) => networkmanager

Comment 6 Pierre Fortin 2016-06-05 20:38:15 CEST
While working on bug 10162 (installed VBox), I needed to logout/login to become member of group vboxusers.

This simple action killed my WiFi again.  "Fixed" by invoking my fixwifi script:

/usr/local/bin/fixwifi:
systemctl stop NetworkManager.service
service network start
Pierre Fortin 2016-06-05 20:40:55 CEST

Summary: wireless will not connect after reboot (for new glibc) => wireless will not connect after reboot(for new glibc) -- also fails after logout/login

Comment 7 Pierre Fortin 2016-06-08 16:46:30 CEST
Installed mga5 on brand new Dell Inspiron 3558.  WiFi works fine on Win10; but is completely dead on mga5.
# rfkill list all
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

However, there is no real switch on this system; only BIOS settings which ARE enabled as witnessed by Win10 working.

# dmesg |grep -i wifi
[   30.827767] Intel(R) Wireless WiFi driver for Linux
[   30.827829] iwlwifi 0000:06:00.0: enabling device (0000 -> 0002)
[   30.828436] iwlwifi 0000:06:00.0: Unsupported splx structure
[   31.285214] iwlwifi 0000:06:00.0: loaded firmware version 25.30.13.0 op_mode iwlmvm
[   31.376675] iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 3160, REV=0x164
[   31.376746] iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
[   31.376969] iwlwifi 0000:06:00.0: RF_KILL bit toggled to disable radio. <=====<<<
[   31.376993] iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
[   32.763016] iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0


ARGH!!!!!!!

Somehow, EITHER Win10 knows how to get around this, and/or Linux is toggling the disable radio bit (see above)...  Getting WiFi working was as ridiculously simple as Fn+PrtScr on this model which is the BIOS-controlled Radio switch (there are NO visual indicators (LEDs) on this system).
Now:
# rfkill list all
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
Comment 8 Pierre Fortin 2016-11-01 16:55:59 CET
This just happened again after logout/login.  This time, my fixwifi script didn't help:
  systemctl stop NetworkManager.service
  service network start

After much analysis of /var/log/messages, found this:
Nov  1 09:43:21 prf network[26560]: Sorry, there is already an instance of ifplugd for wlp3s0 running.

$ ps aux | grep ifplug
root      6226  0.0  0.0   6348  1196 ?        S    Oct10   0:41 /sbin/ifplugd -I -b -i eno1
root     21140  0.0  0.0   6348  1260 ?        S    Oct13   0:35 /sbin/ifplugd -I -b -i wlp3s0

$ kill 21140

$ fixwifi

..and network came up...
Comment 9 Pierre Fortin 2017-09-18 22:19:06 CEST
resolved with official mga6

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME