Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[PARTIALLY SOLVED] Problems with NetworkManager

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

[PARTIALLY SOLVED] Problems with NetworkManager

#1 Post by PrivatePearoak »

Hello, guys! How are you today?

Since last week, i've been having an issue with the Network Manager that is bothering me a little.
Basically my NetworkManager is causing two issues:

1) Everytime i try to reboot or turn off my computer, the NM and WPA Supplicant services will try to stop, but, for some reason, they never do, so my PC will be stuck trying to stop both. I've tried to wait and see and, even after 9 minutes, they won't budge. So i'll be forced to cut the power from my computer.
2) If, for any reason i have to stop or restart the NetworkManager service, they will freeze my terminal and i won't be able to execute any command, even an ls will freeze, and even with other terminal sessions.

In order to try to fix that problem, i tried reinstall the network-manager-gnome, switched to the nm-tray, reinstalled my Wireless card firmware, tried to see any configurations or packages that could be conflicting with the NM. However, till now i didn't have any success on this.

I tried to research on Google, and it turns out that this already happened before, but i couldn't find any conclusive solution.
Did any of you went through this and managed to solve? If so, how did you do?

Thanks in advance for your help guys! ;)
Should my problem be lack of knowledge, i apologize, guys. :x

Here some info that i think it could be useful (if any more is required, pls, let me know)

Code: Select all

lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

Code: Select all

Network portion of inxi
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  vendor: Samsung Co driver: ath10k_pci v: kernel port: f040 bus ID: 01:00.0 
  chip ID: 168c:003e class ID: 0280 
  IF: wlan0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Samsung Co driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 class ID: 0200 
  IF: enp2s0 state: down mac: <filter> 
  Device-3: Qualcomm Atheros QCA61x4 Bluetooth 4.0 type: USB driver: btusb 
  bus ID: 2-4:2 chip ID: 0cf3:e300 class ID: e001 
Last edited by PrivatePearoak on 2021-09-17 11:26, edited 2 times in total.

User avatar
4D696B65
Site admin
Site admin
Posts: 2696
Joined: 2009-06-28 06:09
Been thanked: 85 times

Re: Problems with NetworkManager

#2 Post by 4D696B65 »


PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#3 Post by PrivatePearoak »

Hello there! Thank you for the response!

Yeah, firnware-atheros is already installed. It was the first thing i did when i did a fresh install on my PC, mate.
The problem is with network-manager and wpasupplicant, which prevents my PC of reboot/shutdown or freeze my terminal when i try to stop/restart the NetworkManager service. Unfortunately i couldn't track what exactly is going on. So it seems the problem is with the service itself.

Anyways, here the output of my last test i did few hours ago. As far as my knowledge goes, i didn't see out of the ordinary. I saw an error message, but it seems common with my wireless card, as it used to happen with Debian 10, but the problem i'm mentioning on this topic never happened on it.
The problem happened between 18:18-18:35 (there's a 9 minute gap on the log, which was when i turned off the PC at 18:18 and turned it on a few mins before 18:35)

Code: Select all

journalctl -u NetworkManager | grep -i "Sep 01"

Sep 01 17:00:06 muttley systemd[1]: Starting Network Manager...
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.5291] NetworkManager (version 1.30.0) is starting... (for the first time)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.5291] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.5419] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.5447] manager[0x55560021c010]: monitoring kernel firmware directory '/lib/firmware'.
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.5448] monitoring ifupdown state file '/run/network/ifstate'.
Sep 01 17:00:06 muttley systemd[1]: Started Network Manager.
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7081] hostname: hostname: using hostnamed
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7082] hostname: hostname changed from (none) to "muttley"
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7086] dns-mgr[0x555600211170]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7093] manager[0x55560021c010]: rfkill: Wi-Fi hardware radio set enabled
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7093] manager[0x55560021c010]: rfkill: WWAN hardware radio set enabled
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7123] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-adsl.so)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7231] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7458] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-team.so)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7494] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wifi.so)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7507] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wwan.so)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7511] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7518] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7527] manager: Networking is enabled by state file
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7529] dhcp-init: Using DHCP client 'internal'
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7639] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-settings-plugin-ifupdown.so")
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7640] settings: Loaded settings plugin: keyfile (internal)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7640] ifupdown: management mode: unmanaged
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7641] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7641] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7712] device (lo): carrier: link connected
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7718] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7744] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7879] settings: (enp2s0): created default wired connection 'Wired connection 1'
Sep 01 17:00:06 muttley NetworkManager[595]: <info>  [1630526406.7890] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 17:00:07 muttley NetworkManager[595]: <info>  [1630526407.0417] modem-manager: ModemManager available
Sep 01 17:00:07 muttley NetworkManager[595]: <info>  [1630526407.7971] device (wlan0): driver supports Access Point (AP) mode
Sep 01 17:00:07 muttley NetworkManager[595]: <info>  [1630526407.7979] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 01 17:00:07 muttley NetworkManager[595]: <info>  [1630526407.8027] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
Sep 01 17:00:07 muttley NetworkManager[595]: <info>  [1630526407.8110] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 17:00:09 muttley NetworkManager[595]: <info>  [1630526409.2773] device (wlan0): set-hw-addr: set MAC address to 22:88:EF:EE:B6:67 (scanning)
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6403] device (wlan0): supplicant interface state: internal-starting -> disconnected
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6404] Wi-Fi P2P device controlled by interface wlan0 created
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6406] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6410] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6418] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Sep 01 17:00:10 muttley NetworkManager[595]: <info>  [1630526410.6426] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:10 muttley NetworkManager[595]: <warn>  [1630526410.6449] sup-iface[d6154528830db631,0,wlan0]: call-p2p-cancel: failed with P2P cancel failed
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5098] policy: auto-activating connection 'Diluwipedrita' (e795b66e-ae05-4636-9951-f538ca4edc26)
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5123] device (wlan0): Activation: starting connection 'Diluwipedrita' (e795b66e-ae05-4636-9951-f538ca4edc26)
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5133] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5151] manager: NetworkManager state is now CONNECTING
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5185] device (wlan0): set-hw-addr: reset MAC address to C8:FF:28:F2:2A:17 (preserve)
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5244] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5252] device (wlan0): Activation: (wifi) access point 'Diluwipedrita' has security, but secrets are required.
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5253] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5386] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5393] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5460] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5480] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5492] device (wlan0): Activation: (wifi) connection 'Diluwipedrita' has security, and secrets exist.  No new secrets needed.
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5493] Config: added 'ssid' value 'Diluwipedrita'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5493] Config: added 'scan_ssid' value '1'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5494] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5494] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5495] Config: added 'auth_alg' value 'OPEN'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5495] Config: added 'psk' value '<hidden>'
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5851] device (wlan0): supplicant interface state: interface_disabled -> inactive
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.5852] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.6027] device (wlan0): supplicant interface state: inactive -> scanning
Sep 01 17:00:15 muttley NetworkManager[595]: <info>  [1630526415.6028] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.4972] device (wlan0): supplicant interface state: scanning -> authenticating
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.4972] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.5126] device (wlan0): supplicant interface state: authenticating -> associating
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.5127] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.5379] device (wlan0): supplicant interface state: associating -> 4way_handshake
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.5379] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.6020] device (wlan0): supplicant interface state: 4way_handshake -> completed
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.6020] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Diluwipedrita"
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.6021] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.6023] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:20 muttley NetworkManager[595]: <info>  [1630526420.6030] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 01 17:00:21 muttley NetworkManager[595]: <info>  [1630526421.7789] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 01 17:00:21 muttley NetworkManager[595]: <info>  [1630526421.8413] dhcp6 (wlan0): state changed unknown -> bound
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7203] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7273] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7283] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7296] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7345] manager: NetworkManager state is now CONNECTED_SITE
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7351] policy: set 'Diluwipedrita' (wlan0) as default for IPv6 routing and DNS
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7460] device (wlan0): Activation: successful, device activated.
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7483] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 01 17:00:23 muttley NetworkManager[595]: <info>  [1630526423.7513] manager: startup complete
Sep 01 17:00:24 muttley NetworkManager[595]: <info>  [1630526424.7089] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.18.162
Sep 01 17:00:24 muttley NetworkManager[595]: <info>  [1630526424.7106] policy: set 'Diluwipedrita' (wlan0) as default for IPv4 routing and DNS
Sep 01 17:18:35 muttley NetworkManager[595]: <info>  [1630527515.6272] device (wlan0): disconnecting for new activation request.
Sep 01 17:18:35 muttley NetworkManager[595]: <info>  [1630527515.6273] device (wlan0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Sep 01 17:18:35 muttley NetworkManager[595]: <info>  [1630527515.6278] manager: NetworkManager state is now DISCONNECTING
Sep 01 17:18:35 muttley NetworkManager[595]: <info>  [1630527515.6295] audit: op="connection-activate" uuid="3d9420ee-27e7-4f03-982e-278ed24bdb07" name="Karvalhop" pid=1143 uid=1000 result="success"
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8000] device (wlan0): supplicant interface state: completed -> disconnected
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8000] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8019] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8277] dhcp4 (wlan0): canceled DHCP transaction
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8278] dhcp4 (wlan0): state changed bound -> done
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8283] dhcp6 (wlan0): canceled DHCP transaction
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8284] dhcp6 (wlan0): state changed bound -> done
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8323] device (wlan0): set-hw-addr: set MAC address to EE:53:AD:98:85:63 (scanning)
Sep 01 17:18:38 muttley NetworkManager[595]: <warn>  [1630527518.8326] platform-linux: do-change-link[3]: failure changing link: failure 108 (Cannot send after transport endpoint shutdown)
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8343] manager: NetworkManager state is now DISCONNECTED
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8346] device (wlan0): Activation: starting connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8423] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8431] manager: NetworkManager state is now CONNECTING
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8443] device (wlan0): set-hw-addr: reset MAC address to C8:FF:28:F2:2A:17 (preserve)
Sep 01 17:18:38 muttley NetworkManager[595]: <warn>  [1630527518.8445] platform-linux: do-change-link[3]: failure changing link: failure 108 (Cannot send after transport endpoint shutdown)
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8446] device (wlan0): state change: prepare -> failed (reason 'config-failed', sys-iface-state: 'managed')
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8453] manager: NetworkManager state is now DISCONNECTED
Sep 01 17:18:38 muttley NetworkManager[595]: <warn>  [1630527518.8472] device (wlan0): Activation: failed for connection 'Karvalhop'
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8476] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8484] device (wlan0): set-hw-addr: set MAC address to 46:19:A3:4A:FA:BD (scanning)
Sep 01 17:18:38 muttley NetworkManager[595]: <warn>  [1630527518.8485] platform-linux: do-change-link[3]: failure changing link: failure 108 (Cannot send after transport endpoint shutdown)
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8502] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Sep 01 17:18:38 muttley NetworkManager[595]: <info>  [1630527518.8502] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5254] device (wlan0): Activation: starting connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5256] audit: op="connection-activate" uuid="3d9420ee-27e7-4f03-982e-278ed24bdb07" name="Karvalhop" pid=1143 uid=1000 result="success"
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5258] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5262] manager: NetworkManager state is now CONNECTING
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5267] device (wlan0): set-hw-addr: reset MAC address to C8:FF:28:F2:2A:17 (preserve)
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5342] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5347] device (wlan0): Activation: (wifi) access point 'Karvalhop' has security, but secrets are required.
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5347] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5410] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5430] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5447] device (wlan0): Activation: (wifi) connection 'Karvalhop' has security, and secrets exist.  No new secrets needed.
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5451] Config: added 'ssid' value 'Karvalhop'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5452] Config: added 'scan_ssid' value '1'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5452] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5452] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5452] Config: added 'auth_alg' value 'OPEN'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5453] Config: added 'psk' value '<hidden>'
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5693] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5694] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> disconnected
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5837] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 01 17:18:44 muttley NetworkManager[595]: <info>  [1630527524.5837] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4638] device (wlan0): supplicant interface state: scanning -> authenticating
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4638] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4701] device (wlan0): supplicant interface state: authenticating -> associating
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4702] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4854] device (wlan0): supplicant interface state: associating -> associated
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.4854] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6839] device (wlan0): supplicant interface state: associated -> 4way_handshake
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6840] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6915] device (wlan0): supplicant interface state: 4way_handshake -> completed
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6916] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Karvalhop"
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6917] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6919] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.6923] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7251] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.111
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7268] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7427] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7431] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7436] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7451] manager: NetworkManager state is now CONNECTED_SITE
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7453] policy: set 'Karvalhop' (wlan0) as default for IPv4 routing and DNS
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7468] device (wlan0): Activation: successful, device activated.
Sep 01 17:18:49 muttley NetworkManager[595]: <info>  [1630527529.7476] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 01 18:18:49 muttley NetworkManager[595]: <info>  [1630531129.7286] dhcp4 (wlan0): state changed bound -> extended, address=192.168.0.111
Sep 01 18:29:10 muttley NetworkManager[595]: <info>  [1630531750.7523] modem-manager: ModemManager no longer available
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0837] caught SIGTERM, shutting down normally.
Sep 01 18:29:11 muttley systemd[1]: Stopping Network Manager...
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0852] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0855] manager: NetworkManager state is now DISCONNECTING
Sep 01 18:29:11 muttley NetworkManager[595]: <warn>  [1630531751.0881] dispatcher: (15) failed: Refusing activation, D-Bus is shutting down.
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0885] device (wlan0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0887] dhcp4 (wlan0): canceled DHCP transaction
Sep 01 18:29:11 muttley NetworkManager[595]: <info>  [1630531751.0887] dhcp4 (wlan0): state changed extended -> done
Sep 01 18:31:19 muttley systemd[1]: Starting Network Manager...
Sep 01 18:31:20 muttley NetworkManager[600]: <info>  [1630531880.0582] NetworkManager (version 1.30.0) is starting... (for the first time)
Sep 01 18:31:20 muttley NetworkManager[600]: <info>  [1630531880.0583] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Sep 01 18:31:20 muttley NetworkManager[600]: <info>  [1630531880.0650] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Sep 01 18:31:20 muttley NetworkManager[600]: <info>  [1630531880.0675] manager[0x55e8b5470030]: monitoring kernel firmware directory '/lib/firmware'.
Sep 01 18:31:20 muttley NetworkManager[600]: <info>  [1630531880.0675] monitoring ifupdown state file '/run/network/ifstate'.
Sep 01 18:31:20 muttley systemd[1]: Started Network Manager.
Sep 01 18:34:11 muttley systemd[1]: Starting Network Manager...
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.1896] NetworkManager (version 1.30.0) is starting... (for the first time)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.1897] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Sep 01 18:34:11 muttley systemd[1]: Started Network Manager.
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.2004] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.2076] manager[0x55c4ca9b2030]: monitoring kernel firmware directory '/lib/firmware'.
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.2076] monitoring ifupdown state file '/run/network/ifstate'.
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3490] hostname: hostname: using hostnamed
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3491] hostname: hostname changed from (none) to "muttley"
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3495] dns-mgr[0x55c4ca9a5170]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3503] manager[0x55c4ca9b2030]: rfkill: Wi-Fi hardware radio set enabled
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3503] manager[0x55c4ca9b2030]: rfkill: WWAN hardware radio set enabled
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3529] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-adsl.so)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3607] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3762] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-team.so)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3810] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wifi.so)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3832] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wwan.so)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3841] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3843] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3843] manager: Networking is enabled by state file
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3845] dhcp-init: Using DHCP client 'internal'
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3910] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-settings-plugin-ifupdown.so")
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3910] settings: Loaded settings plugin: keyfile (internal)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3910] ifupdown: management mode: managed
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3911] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.3911] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.4006] device (lo): carrier: link connected
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.4030] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.4165] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.4219] settings: (enp2s0): created default wired connection 'Wired connection 1'
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.4245] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:34:11 muttley NetworkManager[598]: <info>  [1630532051.7007] modem-manager: ModemManager available
Sep 01 18:34:12 muttley NetworkManager[598]: <info>  [1630532052.3162] device (wlan0): driver supports Access Point (AP) mode
Sep 01 18:34:12 muttley NetworkManager[598]: <info>  [1630532052.3172] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 01 18:34:12 muttley NetworkManager[598]: <info>  [1630532052.3204] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
Sep 01 18:34:12 muttley NetworkManager[598]: <info>  [1630532052.3275] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:34:13 muttley NetworkManager[598]: <info>  [1630532053.7922] device (wlan0): set-hw-addr: set MAC address to 86:75:89:AD:69:64 (scanning)
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1739] device (wlan0): supplicant interface state: internal-starting -> disconnected
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1740] Wi-Fi P2P device controlled by interface wlan0 created
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1743] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1748] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1758] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Sep 01 18:34:15 muttley NetworkManager[598]: <info>  [1630532055.1770] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:15 muttley NetworkManager[598]: <warn>  [1630532055.1792] sup-iface[e4efb71ee1382ad3,0,wlan0]: call-p2p-cancel: failed with P2P cancel failed
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0400] policy: auto-activating connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0429] device (wlan0): Activation: starting connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0434] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0448] manager: NetworkManager state is now CONNECTING
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0481] device (wlan0): set-hw-addr: reset MAC address to C8:FF:28:F2:2A:17 (preserve)
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0553] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0561] device (wlan0): Activation: (wifi) access point 'Karvalhop' has security, but secrets are required.
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0562] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0568] sup-iface[e4efb71ee1382ad3,0,wlan0]: wps: type pbc start...
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0660] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0661] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0711] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0724] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0733] device (wlan0): Activation: (wifi) connection 'Karvalhop' has security, and secrets exist.  No new secrets needed.
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0734] Config: added 'ssid' value 'Karvalhop'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0735] Config: added 'scan_ssid' value '1'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0735] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0736] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0736] Config: added 'auth_alg' value 'OPEN'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.0736] Config: added 'psk' value '<hidden>'
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.1084] device (wlan0): supplicant interface state: interface_disabled -> inactive
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.1084] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.1260] device (wlan0): supplicant interface state: inactive -> scanning
Sep 01 18:34:20 muttley NetworkManager[598]: <info>  [1630532060.1261] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0318] device (wlan0): supplicant interface state: scanning -> authenticating
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0335] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0483] device (wlan0): supplicant interface state: authenticating -> associating
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0484] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0498] device (wlan0): supplicant interface state: associating -> associated
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.0499] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3015] device (wlan0): supplicant interface state: associated -> 4way_handshake
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3016] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3327] device (wlan0): supplicant interface state: 4way_handshake -> completed
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3328] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Karvalhop"
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3328] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3330] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3337] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3493] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.111
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3506] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3613] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3617] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3622] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3639] manager: NetworkManager state is now CONNECTED_SITE
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3641] policy: set 'Karvalhop' (wlan0) as default for IPv4 routing and DNS
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3657] device (wlan0): Activation: successful, device activated.
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3671] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 01 18:34:25 muttley NetworkManager[598]: <info>  [1630532065.3683] manager: startup complete
Sep 01 18:39:37 muttley NetworkManager[598]: <info>  [1630532377.7019] modem-manager: ModemManager no longer available
Sep 01 18:39:38 muttley systemd[1]: Stopping Network Manager...
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0827] caught SIGTERM, shutting down normally.
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0843] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0846] manager: NetworkManager state is now DISCONNECTING
Sep 01 18:39:38 muttley NetworkManager[598]: <warn>  [1630532378.0875] dispatcher: (6) failed: Refusing activation, D-Bus is shutting down.
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0879] device (wlan0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0999] dhcp4 (wlan0): canceled DHCP transaction
Sep 01 18:39:38 muttley NetworkManager[598]: <info>  [1630532378.0999] dhcp4 (wlan0): state changed bound -> done
Sep 01 18:39:39 muttley NetworkManager[598]: <info>  [1630532379.2846] manager: NetworkManager state is now DISCONNECTED
Sep 01 18:39:39 muttley NetworkManager[598]: <info>  [1630532379.2901] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Sep 01 18:39:39 muttley NetworkManager[598]: <info>  [1630532379.2947] exiting (success)
Sep 01 18:39:39 muttley systemd[1]: NetworkManager.service: Succeeded.
Sep 01 18:39:39 muttley systemd[1]: Stopped Network Manager.
Sep 01 18:39:39 muttley systemd[1]: NetworkManager.service: Consumed 2.798s CPU time.
Sep 01 18:39:51 muttley systemd[1]: Starting Network Manager...
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.1322] NetworkManager (version 1.30.0) is starting... (for the first time)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.1323] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.1449] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Sep 01 18:39:52 muttley systemd[1]: Started Network Manager.
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.1481] manager[0x55c37740d030]: monitoring kernel firmware directory '/lib/firmware'.
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.1482] monitoring ifupdown state file '/run/network/ifstate'.
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3220] hostname: hostname: using hostnamed
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3221] hostname: hostname changed from (none) to "muttley"
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3229] dns-mgr[0x55c377401170]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3235] manager[0x55c37740d030]: rfkill: Wi-Fi hardware radio set enabled
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3236] manager[0x55c37740d030]: rfkill: WWAN hardware radio set enabled
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3258] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-adsl.so)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3384] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3449] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-team.so)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3586] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wifi.so)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3642] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-wwan.so)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3651] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3655] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3659] manager: Networking is enabled by state file
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3662] dhcp-init: Using DHCP client 'internal'
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3791] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-settings-plugin-ifupdown.so")
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3791] settings: Loaded settings plugin: keyfile (internal)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3791] ifupdown: management mode: managed
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3792] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3792] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3835] device (lo): carrier: link connected
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3839] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3854] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3891] settings: (enp2s0): created default wired connection 'Wired connection 1'
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.3909] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:39:52 muttley NetworkManager[595]: <info>  [1630532392.6480] modem-manager: ModemManager available
Sep 01 18:39:53 muttley NetworkManager[595]: <info>  [1630532393.3899] device (wlan0): driver supports Access Point (AP) mode
Sep 01 18:39:53 muttley NetworkManager[595]: <info>  [1630532393.3909] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 01 18:39:53 muttley NetworkManager[595]: <info>  [1630532393.3943] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
Sep 01 18:39:53 muttley NetworkManager[595]: <info>  [1630532393.4015] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:39:54 muttley NetworkManager[595]: <info>  [1630532394.8371] device (wlan0): set-hw-addr: set MAC address to 76:25:47:1E:8B:E1 (scanning)
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2235] device (wlan0): supplicant interface state: internal-starting -> disconnected
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2236] Wi-Fi P2P device controlled by interface wlan0 created
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2241] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2246] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2257] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Sep 01 18:39:56 muttley NetworkManager[595]: <info>  [1630532396.2269] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 01 18:39:56 muttley NetworkManager[595]: <warn>  [1630532396.2274] sup-iface[e69164561abbc0b5,0,wlan0]: call-p2p-cancel: failed with P2P cancel failed
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.0916] policy: auto-activating connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.0932] device (wlan0): Activation: starting connection 'Karvalhop' (3d9420ee-27e7-4f03-982e-278ed24bdb07)
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.0936] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.0953] manager: NetworkManager state is now CONNECTING
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.0993] device (wlan0): set-hw-addr: reset MAC address to C8:FF:28:F2:2A:17 (preserve)
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1047] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1054] device (wlan0): Activation: (wifi) access point 'Karvalhop' has security, but secrets are required.
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1055] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1060] sup-iface[e69164561abbc0b5,0,wlan0]: wps: type pbc start...
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1138] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1139] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1209] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1223] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1234] device (wlan0): Activation: (wifi) connection 'Karvalhop' has security, and secrets exist.  No new secrets needed.
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1239] Config: added 'ssid' value 'Karvalhop'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1244] Config: added 'scan_ssid' value '1'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1247] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1248] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1249] Config: added 'auth_alg' value 'OPEN'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1249] Config: added 'psk' value '<hidden>'
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1454] device (wlan0): supplicant interface state: interface_disabled -> inactive
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1454] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1582] device (wlan0): supplicant interface state: inactive -> scanning
Sep 01 18:40:01 muttley NetworkManager[595]: <info>  [1630532401.1583] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0561] device (wlan0): supplicant interface state: scanning -> authenticating
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0562] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0915] device (wlan0): supplicant interface state: authenticating -> associating
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0916] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0922] device (wlan0): supplicant interface state: associating -> associated
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.0923] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3100] device (wlan0): supplicant interface state: associated -> completed
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3100] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Karvalhop"
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3100] device (p2p-dev-wlan0): supplicant management interface state: associated -> completed
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3102] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3107] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3293] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.111
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3307] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3423] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3427] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3434] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3458] manager: NetworkManager state is now CONNECTED_SITE
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3459] policy: set 'Karvalhop' (wlan0) as default for IPv4 routing and DNS
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3475] device (wlan0): Activation: successful, device activated.
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3485] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 01 18:40:06 muttley NetworkManager[595]: <info>  [1630532406.3494] manager: startup complete

This is the output of a moment that my PC was stuck during a shutdown.

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#4 Post by PrivatePearoak »

Hello again, guys!

I discovered something quite interesting about my issue.

If i ain't mistaken, the NetworkManager service operates the wpa_supplicant service, right? I mean, for the NM to stop, it has to stop the wpa_supplicant as well.
Well, it turns out i decided to manually stop the wpa_supplicant service and THEN restart the NM (in order to replicate the freezing terminal problem).

For my surprise, the problem didn't happen and i could turn off the computer and use my terminal without any problem. So it seems that it's something about the NM manipulating the WPASupplicant service.

As a temporary solution, i wrote a sh file to stop the wpa_supplicant service before turning off the computer.
I did a few tests here and, so far, no problems. I'll keep testing and, should new info come, i will write once again here.

But it seems that it's something related to the NM service using WPASupplicant service that is causing the issue.

For now, i won't mark the post as [SOLVED] to see how everything goes.

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#5 Post by PrivatePearoak »

Hello guys! How are you today?

I'm still testing shutting down my computer with the sh i wrote, which stops wpa_supplicant service before shutting down/rebooting. So far, i didn't have any problems aside from, sometimes, my computer taking some time to stop the service. I noticed that sometimes takes almost 1 minute to stop the service, while others stop almost immediately. But the freezing problem didn't happen once after i did this.

It didn't SOLVE my problem, because, ideally, the service was supposed to stop by itself on a shutdown, but it was a way of bypassing the problem.

It also came to my attention that other users are getting a similar problem with different services. Maybe it could be something wrong with systemd?
Anyways, if i didn't get the problem till Sep 9th, i'll mark the issue as solved.

arzgi
Posts: 1183
Joined: 2008-02-21 17:03
Location: Finland
Been thanked: 31 times

Re: Problems with NetworkManager

#6 Post by arzgi »

Some years ago I had similar issues with network manager and wpa_supplicant. I purged network-manager, and have avoided that ever since.

Here have been many threads recently about wifi issues. There are many options also without network manager.

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#7 Post by PrivatePearoak »

arzgi wrote: 2021-09-05 14:51 Some years ago I had similar issues with network manager and wpa_supplicant. I purged network-manager, and have avoided that ever since.

Here have been many threads recently about wifi issues. There are many options also without network manager.
Yeah, i tried to do this, mate, but the problem still kept up till i made my sh file to stop wpa_supplicant before NM.
Tbh apart from NM, i only used wicd (which, due to the deprecation of Python 2, it was removed from Debian repos). So i don't know anything aside from those two.
Do you have any suggestions of replacements for NM?

I'm still not sure if the problem is with wpa_supplicant alone or nm using the former. I guess trying something different could help me understand the problem better.

paxmark1
Posts: 54
Joined: 2008-10-23 05:19
Has thanked: 1 time

Re: Problems with NetworkManager

#8 Post by paxmark1 »

Replacements - Lxqt went with connman (connmanctl) . A lot of the code is from Intel employees. It worked for me in lxqt and also for I3 and Sway on atom cpu netbooks, netboxes. Just a hunch, but depending on your DE it could be more of problem to switch to connman than the solution. I did a quick look at BTS for wpasupplicant and did not see anything.

I leave the systemd solutions to others. Hoas has written up about those options previous.

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#9 Post by PrivatePearoak »

paxmark1 wrote: 2021-09-05 23:22 Replacements - Lxqt went with connman (connmanctl) . A lot of the code is from Intel employees. It worked for me in lxqt and also for I3 and Sway on atom cpu netbooks, netboxes. Just a hunch, but depending on your DE it could be more of problem to switch to connman than the solution. I did a quick look at BTS for wpasupplicant and did not see anything.

I leave the systemd solutions to others. Hoas has written up about those options previous.
I was thinking on trying Connman, but due to my daily routine, i couldn't do it just yet. Tbh, i'm also afraid of making things even worse if i change to Connman, so, if you happen to know anything about Connman on an XFCE environment, i'd appreciate it!
Otherwise, i'll just try and see (*gulp*)! hahahaha

I researched on Google about any issues with wpa_supplicant and it seemed a problem that happened with distros using the 5.4 kernel version and i saw mostly with Manjaro and Arch Linux users. I saw one or two threads with Ubuntu or Mint. However, with Debian and/or with the 5.10 kernel version, i didn't see anything. :(

Well, in any case, the sh file i wrote is helping to bypass this issue. So far i'm watching its behavior and, for now, it's working. So i guess in few days i'll mark this thread as solved.

User avatar
cds60601
df -h | participant
df -h | participant
Posts: 698
Joined: 2017-11-25 05:58
Location: Florida
Has thanked: 129 times
Been thanked: 59 times

Re: Problems with NetworkManager

#10 Post by cds60601 »

PrivatePearoak wrote: 2021-09-06 15:45
paxmark1 wrote: 2021-09-05 23:22 Replacements - Lxqt went with connman (connmanctl) . A lot of the code is from Intel employees. It worked for me in lxqt and also for I3 and Sway on atom cpu netbooks, netboxes. Just a hunch, but depending on your DE it could be more of problem to switch to connman than the solution. I did a quick look at BTS for wpasupplicant and did not see anything.

I leave the systemd solutions to others. Hoas has written up about those options previous.
I was thinking on trying Connman, but due to my daily routine, i couldn't do it just yet. Tbh, i'm also afraid of making things even worse if i change to Connman, so, if you happen to know anything about Connman on an XFCE environment, i'd appreciate it!
Otherwise, i'll just try and see (*gulp*)! hahahaha

I researched on Google about any issues with wpa_supplicant and it seemed a problem that happened with distros using the 5.4 kernel version and i saw mostly with Manjaro and Arch Linux users. I saw one or two threads with Ubuntu or Mint. However, with Debian and/or with the 5.10 kernel version, i didn't see anything. :(

Well, in any case, the sh file i wrote is helping to bypass this issue. So far i'm watching its behavior and, for now, it's working. So i guess in few days i'll mark this thread as solved.
I too had issues with NetworkManager so I replaced it with Connman. So far, it's working well. Not sure what kind of mileage you'll get as I have mine working with DWM.
It seems pretty straight forward and so far, I'm pretty happy with it (mainly since I really no longer have a need to compile in a system tray in my DWM).
Supercalifragilisticexpialidocious

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: Problems with NetworkManager

#11 Post by PrivatePearoak »

Hello guys, long time no see! My apologies for not answering for such a long time.

Yeah, so far my script is working fine. Of all times i tried to reboot/shutdown, only once i got frozen with it. It didn't SOLVE the problem, but at least it became way less often. But what i could tell is that the true culprit is the wpa_supplicant service, not the NetworkManager per se. But since i only had the problem once after i wrote the script, i guess i could mark this thread as solved.

About the connman, i still didn't try it, since my last weeks are being pretty crazy. hahaha
Anyways, once things settle down a little, i'll try connman and hope that the issue won't happen. However, if the problem is the wpa_supplicant, i'm a little afraid though. hahahaha
I hope i can bring the results anytime soon.

Anyways, thanks for all the support guys! ;)

User avatar
bw123
Posts: 4015
Joined: 2011-05-09 06:02
Has thanked: 1 time
Been thanked: 28 times

Re: [PARTIALLY SOLVED] Problems with NetworkManager

#12 Post by bw123 »

Can you add somemore info in case other people find the thread later on?

Code: Select all

apt policy network-manager wpasupplicant
nmcli --terse
Are there any network filesystems mounted when it hangs, or anything in background using the connection?

I still use NetworkManager on bullseye, it's quite a bit better than couple of years ago. Still aggravates me too occasionally.

Thanks
resigned by AI ChatGPT

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: [PARTIALLY SOLVED] Problems with NetworkManager

#13 Post by PrivatePearoak »

bw123 wrote: 2021-09-17 12:04 Can you add somemore info in case other people find the thread later on?

Code: Select all

apt policy network-manager wpasupplicant
nmcli --terse
Are there any network filesystems mounted when it hangs, or anything in background using the connection?

I still use NetworkManager on bullseye, it's quite a bit better than couple of years ago. Still aggravates me too occasionally.

Thanks
Hello there!

Nope, i didn't do any specific setting on Network Manager, i simply installed it and configured to allow my Wireless to work (commenting some lines at /etc/network/interfaces).
No extra filesystem not anything. About the two commands you've mentioned, here are their outputs. Btw, could you explain them to me, so i could learn some more about them? :D

Also, aside from the two commands you mentioned, are there any others i can run?
Attachments
nmcli.png
nmcli.png (121.84 KiB) Viewed 3583 times
apt policy.png
apt policy.png (54.31 KiB) Viewed 3583 times

User avatar
sunrat
Administrator
Administrator
Posts: 6382
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 115 times
Been thanked: 456 times

Re: [PARTIALLY SOLVED] Problems with NetworkManager

#14 Post by sunrat »

Please copy/paste terminal text in CODE tags rather than posting images.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: [PARTIALLY SOLVED] Problems with NetworkManager

#15 Post by PrivatePearoak »

sunrat wrote: 2021-09-18 02:22 Please copy/paste terminal text in CODE tags rather than posting images.
My apologies, my friend.
Here's the code block then (with few modifications).

Code: Select all

apt policy network-manager wpasupplicant
network-manager:
  Installed: 1.30.0-2
  Candidate: 1.30.0-2
  Version table:
 *** 1.30.0-2 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
wpasupplicant:
  Installed: 2:2.9.0-21
  Candidate: 2:2.9.0-21
  Version table:
 *** 2:2.9.0-21 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status

Code: Select all

"Qualcomm Atheros QCA6174"
	wifi (ath10k_pci), XX:XX:XX:XX:XX:XX, hw, mtu 1500
	ip4 default
	inet4 192.168.0.111/24
	route4 0.0.0.0/0
	route4 192.168.0.0/24
	route4 169.254.0.0/16
	inet6 XXXX::XXXX:XXXX:XXXX:XXXX/64
	route6 fe80::/64
	route6 ff00::/8

p2p-dev-wlan0: disconnected
	"p2p-dev-wlan0"
	wifi-p2p, hw

enp2s0: unavailable
	"Realtek RTL8111/8168/8411"
	ethernet (r8169), XX:XX:XX:XX:XX:XX, hw, mtu 1500

lo: unmanaged
	"lo"
	loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
	servers: 192.168.0.1
	interface: wlan0

PrivatePearoak
Posts: 22
Joined: 2021-08-19 02:18

Re: [PARTIALLY SOLVED] Problems with NetworkManager

#16 Post by PrivatePearoak »

Anyways, to those who might be interest in how i "solved" the problem, i simply wrote a script that stops the wpasupplicant service before shutting down or reboot and i create a symlink to execute it, like this:

Code: Select all

#!/bin/bash
sudo systemctl stop wpa_supplicant
sudo systemctl stop NetworkManager #Not mandatory, but it seemed a safer option for shutting down the computer
sudo init 0 #Could also be "sudo init 6" for rebooting
Of course, without it, the problem still keeps happening, but at least it's an option for not having to reinstall or until you don't know how to completely solve the problem.

Post Reply