[Bug 967427] New: No wireless LANs shown in NetworkManager after installing today's patches for wpa-supplicant (and glibc)
http://bugzilla.opensuse.org/show_bug.cgi?id=967427 Bug ID: 967427 Summary: No wireless LANs shown in NetworkManager after installing today's patches for wpa-supplicant (and glibc) Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: Willy.Weisz@univie.ac.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installing today's patches for glibc and wpa-supplicant NetworkManager stopped finding wireless LANs. /var/log/NetworkManager shows the following entries after restarting the network and the WLAN in NetworkManager (inserted blank lines show where LAN interface related messages were deleted): 2016-02-19T16:00:13.011799+01:00 alsefer NetworkManager[1541]: <info> enable requested (sleeping: no enabled: no) 2016-02-19T16:00:13.012228+01:00 alsefer NetworkManager[1541]: <info> waking up and re-enabling... 2016-02-19T16:00:13.228076+01:00 alsefer NetworkManager[1541]: <info> NetworkManager state is now DISCONNECTED 2016-02-19T16:00:13.228708+01:00 alsefer NetworkManager[1541]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] 2016-02-19T16:00:13.229327+01:00 alsefer NetworkManager[1541]: <info> (wlo1): bringing up device. 2016-02-19T16:00:13.229931+01:00 alsefer NetworkManager[1541]: <info> (wlo1): deactivating device (reason 'managed') [2] 2016-02-19T16:00:14.847921+01:00 alsefer NetworkManager[1541]: <info> (wlo1): bringing up device. 2016-02-19T16:00:14.885134+01:00 alsefer NetworkManager[1541]: <info> WiFi hardware radio set enabled 2016-02-19T16:00:14.885708+01:00 alsefer NetworkManager[1541]: <info> WiFi now enabled by radio killswitch 2016-02-19T16:00:14.886176+01:00 alsefer NetworkManager[1541]: <info> (wlo1): bringing up device. 2016-02-19T16:00:19.126812+01:00 alsefer NetworkManager[1541]: <info> NetworkManager state is now CONNECTING 2016-02-19T16:00:20.139285+01:00 alsefer NetworkManager[1541]: <info> NetworkManager state is now CONNECTED_GLOBAL 2016-02-19T16:00:39.897674+01:00 alsefer NetworkManager[1541]: <error> [1455894039.897539] [nm-supplicant-interface.c:1021] interface_add_cb(): (wlo1): error adding interface: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 2016-02-19T16:00:39.898372+01:00 alsefer NetworkManager[1541]: dbus_g_proxy_cancel_call: assertion 'pending != NULL' failed 2016-02-19T16:00:39.898677+01:00 alsefer NetworkManager[1541]: <info> (wlo1): supplicant interface state: starting -> down 2016-02-19T16:00:39.899011+01:00 alsefer NetworkManager[1541]: <warn> Trying to remove a non-existant call id. The WLAN connection worked perfectly before I installed today's patches. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
Willy Weisz
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
Willy Weisz
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c1
--- Comment #1 from Willy Weisz
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c3
Alick Gardiner
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c4
--- Comment #4 from Alick Gardiner
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c6
--- Comment #6 from Willy Weisz
I've received various complains about the problems of this glibc patch recently. Not only opensuse, including Arch and Debian. And the problems are not the same and various people saw various issues, and not all people encountered it. But let me make it simply, people encountered various problem after installed this patch.
Since I can't reproduce it, and there're no unique solution from me, here I just list successful solution for you:
1. They found there're another glibc appears in their lib path, which makes their problem crashed, and it's fixed when they removed it.
2. They found the dependencies of Python encountered crash after installed the glibc patch. And it's fixed after they re-installed the related dependencies.
Hope this information is helpful for you. And please feedback here if you solved it, and tell us how.
Thanks!
Here is the feedback: glibc isn't the culprit, it's wpa_supplicant 2.5.73 (and also 74) which was proposed by the online update at the same time as the glibc update (wpa_supplicant 2.5.x is in the directory repositories/hardware/openSUSE_13.1h I inluded in my YaST configuration). Reverting to wpa_supplicant 2.0 as provided by the openSuSE release 13.1 - the status before the unfortunate online update - solved the problem! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c7
--- Comment #7 from Alick Gardiner
http://bugzilla.opensuse.org/show_bug.cgi?id=967427
http://bugzilla.opensuse.org/show_bug.cgi?id=967427#c11
Karl Cheng
participants (1)
-
bugzilla_noreply@novell.com