Your message dated Sat, 8 Oct 2016 21:30:36 -0700
with message-id
<caouib5moc07ou8gptgvlbwlpyntpcifr1o1o9l2d0kay_zg...@mail.gmail.com>
and subject line fixed
has caused the Debian Bug report #839794,
regarding network-manager: wifi networks not re-scanned after disabling and
enabling device
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
839794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839794
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.4.0-4
Severity: important
Hi. I just upgraded stretch and got the new 4.7 kernel.
I have a Thinkpad X1 Carbon. Fn-F8 is the wifi hardware killswitch.
When I first boot the machine, I see wifi networks in the Network
Manager applet.
If I disable wifi with Fn-F8, and re-enable wifi with Fn-F8, I see no networks.
Before the upgrade, when I re-enabled wifi it would scan available
networks and display them.
Now it displays nothing. I cannot connect to anything. I can't
choose any of my saved network connections, either.
It is going to be inconvenient to reboot every time I need to use
wifi. I prefer to turn the device off when I am not using it.
Maybe the log below is relevant. I tried disabling and re-enabling
again. A pending scan from the previous time got stuck?
Is this related to the other bugs about randomly generating the MAC?
How do I turn that off? I don't need that. Wouldn't it make me seem
like I am a hostile node, to always be faking my MAC? The whole
purpose of a MAC address is to have unique identifiers for each
hardware device on a network, so that it isn't likely for two devices
to try to use the same MAC and collide. Randomly changing the MAC as
a default policy increases the possibility of MAC collisions.
Thanks.
Mark
Oct 4 16:51:22 walnut wpa_supplicant[2659]: rfkill: WLAN soft blocked
Oct 4 16:51:22 walnut wpa_supplicant[2659]: rfkill: WLAN soft blocked
Oct 4 16:51:22 walnut NetworkManager[3952]: <info> [1475625082.1684]
manager: WiFi now disabled by radio killswitch
Oct 4 16:51:22 walnut wpa_supplicant[2659]: nl80211: deinit
ifname=p2p-dev-wlp4s0 disabled_11b_rates=0
Oct 4 16:51:22 walnut NetworkManager[3952]: <info> [1475625082.1685]
device (wlp4s0): state change: disconnected -> unavailable (reason
'none') [30 20 0]
Oct 4 16:51:22 walnut systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 4 16:51:22 walnut systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 4 16:51:22 walnut wpa_supplicant[2659]: nl80211: deinit
ifname=wlp4s0 disabled_11b_rates=0
Oct 4 16:51:31 walnut NetworkManager[3952]: <info> [1475625091.5192]
manager: WiFi now enabled by radio killswitch
Oct 4 16:51:31 walnut kernel: [ 1102.716085] iwlwifi 0000:04:00.0: L1
Enabled - LTR Enabled
Oct 4 16:51:31 walnut kernel: [ 1102.717372] iwlwifi 0000:04:00.0: L1
Enabled - LTR Enabled
Oct 4 16:51:31 walnut systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 4 16:51:31 walnut systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 4 16:51:31 walnut kernel: [ 1102.849546] iwlwifi 0000:04:00.0: L1
Enabled - LTR Enabled
Oct 4 16:51:31 walnut kernel: [ 1102.850070] iwlwifi 0000:04:00.0: L1
Enabled - LTR Enabled
Oct 4 16:51:31 walnut kernel: [ 1102.931906] IPv6:
ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct 4 16:51:31 walnut NetworkManager[3952]: <info> [1475625091.7941]
sup-iface[0x123b6e0,wlp4s0]: supports 5 scan SSIDs
Oct 4 16:51:31 walnut NetworkManager[3952]: <info> [1475625091.7952]
device (wlp4s0): supplicant interface state: starting -> ready
Oct 4 16:51:31 walnut NetworkManager[3952]: <info> [1475625091.7953]
device (wlp4s0): state change: unavailable -> disconnected (reason
'supplicant-available') [20 30 42]
Oct 4 16:51:31 walnut kernel: [ 1102.989589] IPv6:
ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct 4 16:51:34 walnut NetworkManager[3952]: <info> [1475625094.8022]
device (wlp4s0): supplicant interface state: ready -> inactive
Oct 4 16:51:57 walnut NetworkManager[3952]: <info> [1475625117.8568]
device (wlp4s0): set-hw-addr: set MAC address to EE:B3:9D:D5:69:D6
(scanning)
Oct 4 16:51:57 walnut kernel: [ 1129.063086] IPv6:
ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Oct 4 16:51:57 walnut NetworkManager[3952]: <info> [1475625117.8685]
device (wlp4s0): supplicant interface state: inactive -> disabled
Oct 4 16:51:57 walnut NetworkManager[3952]: <info> [1475625117.8981]
device (wlp4s0): supplicant interface state: disabled -> inactive
Oct 4 16:51:57 walnut wpa_supplicant[2659]: wlp4s0: Reject scan
trigger since one is already pending
ct 4 16:53:34 walnut NetworkManager[3952]: <info> [1475625214.7814]
device (wlp4s0): supplicant interface state: inactive -> scanning
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.115
ii dbus 1.10.10-1
ii init-system-helpers 1.45
ii libaudit1 1:2.6.7-1
ii libbluetooth3 5.36-1+b2
ii libc6 2.24-3
ii libglib2.0-0 2.50.0-1
ii libgnutls30 3.5.4-2
ii libgudev-1.0-0 230-3
ii libmm-glib0 1.6.2-1
ii libndp0 1.6-1
ii libnewt0.52 0.52.18-3
ii libnl-3-200 3.2.27-1
ii libnm0 1.4.0-4
ii libpam-systemd 231-4
ii libpolkit-agent-1-0 0.105-16
ii libpolkit-gobject-1-0 0.105-16
ii libreadline6 6.3-8+b4
ii libselinux1 2.5-3
ii libsoup2.4-1 2.56.0-1
ii libsystemd0 231-4
ii libteamdctl0 1.26-1
ii libuuid1 2.28.2-1
ii lsb-base 9.20160629
ii policykit-1 0.105-16
ii udev 231-4
ii wpasupplicant 2.5-2+v2.4-3
Versions of packages network-manager recommends:
ii crda 3.13-1+b1
ii dnsmasq-base 2.76-4
ii iptables 1.6.0-3
ii iputils-arping 3:20150815-2
ii isc-dhcp-client 4.3.5~b1-1
ii modemmanager 1.6.2-1
ii ppp 2.4.7-1+3
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
I don't know why the bug was fixed, but it works now.
When I wake the machine from suspend, I see all the networks.
When I disable with the hardware killswitch and then re-enable, it
scans the networks.
Thanks. -Mark
--- End Message ---
