Wifi problem and reboot/shutdown process problem after waking from sleep (vivobook K3500PA)

Hello community!

Linux nab here(another one), I have installed Manjaro KDE Plasma on my ASUS Vivobook K3500PA and I have a major issue with the “sleep / suspend” on this OS. After waking the laptop from sleep the wifi just disconnects and it can’t find/list any network and if I try to either reboot or shutdown the laptop it will start the reboot/shutdown process and then it just stays like that and I have to force shutdown the laptop by pressing and holding the power button for 10 seconds in order to get it working again (again, this happens ONLY after waking from sleep, if I don’t do that it can reboot/shutdown without issues). I have tried with the preinstalled recommended 5.15 kernel and the 5.17.9-1 version and I have also tested with Manjaro Gnome but the problem is the same regardless of what kernel / manjaro distro I use and this is a big problem since I really want to start using Manjaro on my laptop and get used with linux but if i don’t manage to fix this I’ll be forced to roll back to microsoft…

Edit as per @brahma 's instructions:

System:
  Kernel: 5.15.41-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=30fa660d-aa41-4720-aa5f-0db25a371d87 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop X3500PA_K3500PA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X3500PA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: X3500PA.300 date: 10/04/2021
Battery:
  ID-1: BAT0 charge: 62.6 Wh (100.0%) condition: 62.6/63.0 Wh (99.3%)
    volts: 12.0 min: 12.0 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: discharging cycles: 46
CPU:
  Info: model: 11th Gen Intel Core i7-11370H bits: 64 type: MT MCP
    arch: Tiger Lake family: 6 model-id: 0x8C (140) stepping: 1 microcode: 0xA4
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 755 high: 1021 min/max: 400/4800 scaling:
    driver: intel_pstate governor: powersave cores: 1: 932 2: 521 3: 587 4: 943
    5: 827 6: 628 7: 588 8: 1021 bogomips: 52856
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel ports: active: eDP-1 empty: DP-1,HDMI-A-1
    bus-ID: 0000:00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
    bus-ID: 3-6:3 chip-ID: 13d3:5458 class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: Samsung 0x4161 built: 2020 res: 1920x1080 hz: 60
    dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 22.0.4
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
    bus-ID: 0000:00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.41-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel bus-ID: 0000:2d:00.0
    chip-ID: 14c3:7961 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 3-10:6 chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
  Local Storage: total: 953.87 GiB used: 10.6 GiB (1.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2210 MTFDHBA1T0QFD
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: P6MA007 temp: 39.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 953.57 GiB size: 937.53 GiB (98.32%) used: 10.6 GiB (1.1%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 2000
Info:
  Processes: 231 Uptime: 5m wakeups: 450 Memory: 15.33 GiB
  used: 1.28 GiB (8.4%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1198 lib: 334 flatpak: 0
  Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16

journalctl --boot=0 --priority=3 --no-pager
iun 06 20:50:11 Alex-Laptop kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
iun 06 20:50:11 Alex-Laptop kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
iun 06 20:50:11 Alex-Laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20210730/psargs-330)
iun 06 20:50:11 Alex-Laptop kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
iun 06 20:50:11 Alex-Laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20210730/psargs-330)
iun 06 20:50:11 Alex-Laptop kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
iun 06 20:50:11 Alex-Laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20210730/psargs-330)
iun 06 20:50:11 Alex-Laptop kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
iun 06 20:50:11 Alex-Laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20210730/psargs-330)
iun 06 20:50:11 Alex-Laptop kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
iun 06 20:50:11 Alex-Laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20210730/psargs-330)
iun 06 20:50:11 Alex-Laptop kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
iun 06 20:50:14 Alex-Laptop systemd[603]: Failed to start Update XDG user dir configuration.

edit your post, click on this icon in editor: </> and put the inxi -Fazy output inside
also post output from logs:
journalctl --boot=0 --priority=3 --no-pager

1 Like

try installing the 5.18 kernel, and test with it

1 Like

I just did, problem persists sadly…

so did you also reboot your pc just right now?

Yes I did, I know I need to reboot to get the kernel running.

i meant something different… so so try to put your pc to sleep and after waking up when the wifi doesnt work provide logs after you put your pc to sleep - search for log that starts with suspending or something like that, and copy those logs here:
journalctl --boot=0 --priority=5 --no-pager

1 Like

Ok I’ll do that as soon as I get home, I’m at work rn :+1:

also do this open terminal nad run thsi command:

journalctl --boot 0 --unit NetworkManager.service --follow --no-hostname

then suspend your pc, while the terminal is still open
wake up pc, and check the logs in the terminal

1 Like

Yes sir will do

ok I did as you said and I did find something interesting;
so after running journalctl --boot=0 --priority=5 --no-pager i found this:

iun 07 19:01:23 Alex-Laptop kscreenlocker_greet[1686]: Qt: Session management error: networkIdsList argument is NULL
iun 07 19:01:23 Alex-Laptop kscreenlocker_greet[1686]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_US" . Search paths ("/usr/share/qt/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")
iun 07 19:01:23 Alex-Laptop kscreenlocker_greet[1686]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool
iun 07 19:01:23 Alex-Laptop kernel: audit: type=1334 audit(1654617683.539:104): prog-id=0 op=UNLOAD
iun 07 19:02:59 Alex-Laptop kernel: queueing ieee80211 work while going to suspend
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: can't change power state from D3cold to D0 (config space inaccessible)
iun 07 19:02:59 Alex-Laptop kernel: pcieport 10000:e0:1d.0: can't derive routing for PCI INT A
iun 07 19:02:59 Alex-Laptop kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: can't change power state from D3cold to D0 (config space inaccessible)
iun 07 19:02:59 Alex-Laptop kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -5
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: PM: failed to resume async: error -5
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: driver own failed
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: chip reset
iun 07 19:02:59 Alex-Laptop kernel: mt7921e 0000:2d:00.0: Message 00000046 (seq 12) timeout
iun 07 19:02:59 Alex-Laptop kernel: ------------[ cut here ]------------
iun 07 19:02:59 Alex-Laptop kernel: Hardware became unavailable upon resume. This could be a software issue prior to suspend or a hardware issue.

so there is something wrong with the drivers for my mt7921e network card apparently, is this even fixable without a driver fix from either the manufacturer or manjaro devs?

and this is what I got after running journalctl --boot 0 --unit NetworkManager.service --follow --no-hostname:

journalctl --boot 0 --unit NetworkManager.service --follow --no-hostname                       ✔

iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2465] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2544] dhcp4 (wlo1): state changed new lease, address=192.168.0.182
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2612] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2632] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2632] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2634] manager: NetworkManager state is now CONNECTED_LOCAL
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2638] manager: NetworkManager state is now CONNECTED_SITE
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2639] policy: set 'Schmitz' (wlo1) as default for IPv4 routing and DNS
iun 07 18:58:55 NetworkManager[431]: <info>  [1654617535.2669] device (wlo1): Activation: successful, device activated.
iun 07 18:58:56 NetworkManager[431]: <info>  [1654617536.3722] manager: NetworkManager state is now CONNECTED_GLOBAL
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.0089] manager: sleep: sleep requested (sleeping: no  enabled: yes)
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.0091] manager: NetworkManager state is now ASLEEP
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.0093] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.3861] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.4223] dhcp4 (wlo1): canceled DHCP transaction
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.4225] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.4225] dhcp4 (wlo1): state changed no lease
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.4440] device (wlo1): set-hw-addr: set MAC address to DA:92:CC:43:51:5B (scanning)
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.5264] device (wlo1): supplicant interface state: completed -> disconnected
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.5265] device (wlo1): supplicant interface state: disconnected -> interface_disabled
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.5265] device (wlo1): supplicant interface state: interface_disabled -> disconnected
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.5267] device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
iun 07 19:01:23 NetworkManager[431]: <info>  [1654617683.5649] device (wlo1): set-hw-addr: reset MAC address to 48:E7:DA:29:C4:33 (unmanage)
iun 07 19:02:59 NetworkManager[431]: <info>  [1654617779.5114] manager: sleep: wake requested (sleeping: yes  enabled: yes)
iun 07 19:02:59 NetworkManager[431]: <info>  [1654617779.5115] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

so put your pc to sleep, wake up and run these commands:
sudo modprobe -r mt7921e
sudo modprobe mt7921e
sudo systemctl restart NetworkManager
and see if you have wifi

1 Like

after waking from sleep and running
sudo modprobe -r mt7921e
the terminal gets stuck at that command (it just does nothing) and if i force close the terminal while the process is “running” and run
sudo systemctl restart NetworkManager
it gets stuck again just like it did with the previous command so no luck…

just looked it up and there are bug reports with the same issue you have with the same wifi, wifi not working after sleep… so it will be fixed but i have no idea when…
and to that freezing when trying to reboot after you wake up, can you reboot normally before you put your pc to sleep?

oh so it’s a known issue, that’s good to know.

yes, it works perfectly fine if i don’t put it to sleep

ok, so it is related to the wifi … and how long does it takes to reboot? you should wait at least 3 minutes before you force it…

I’ll run a test now with a timer and report back

ok so I left it for 10 minutes now before I force closed it so yeah my bet is that I could leave it over night and it would still not reboot. I’m gonna attach a photo of what I had on screen while waiting to reboot if it’s gonna help with anything.

ok, run this command:
journalctl --boot=-1 --no-pager
and check logs after system is powering down

not sure if this is the right info but here goes:

iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: State 'stop-sigterm' timed out. Killing.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Killing process 655 (systemd) with signal SIGKILL.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Killing process 1338 (xdg-desktop-por) with signal SIGKILL.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Killing process 944 (at-spi-bus-laun) with signal SIGKILL.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Main process exited, code=killed, status=9/KILL
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Killing process 1338 (xdg-desktop-por) with signal SIGKILL.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Killing process 944 (at-spi-bus-laun) with signal SIGKILL.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Failed with result 'timeout'.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Unit process 1338 (xdg-desktop-por) remains running after unit stopped.
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Unit process 944 (at-spi-bus-laun) remains running after unit stopped.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped User Manager for UID 1000.
iun 07 21:18:57 Alex-Laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
iun 07 21:18:57 Alex-Laptop systemd[1]: user@1000.service: Consumed 1.614s CPU time.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopping User Runtime Directory /run/user/1000...
iun 07 21:18:57 Alex-Laptop kernel: audit: type=1131 audit(1654625937.103:127): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
iun 07 21:18:57 Alex-Laptop systemd[1]: run-user-1000.mount: Deactivated successfully.
iun 07 21:18:57 Alex-Laptop systemd[1]: Unmounted /run/user/1000.
iun 07 21:18:57 Alex-Laptop systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped User Runtime Directory /run/user/1000.
iun 07 21:18:57 Alex-Laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:18:57 Alex-Laptop systemd[1]: Removed slice User Slice of UID 1000.
iun 07 21:18:57 Alex-Laptop systemd[1]: user-1000.slice: Consumed 12.122s CPU time.
iun 07 21:18:57 Alex-Laptop kernel: audit: type=1131 audit(1654625937.109:128): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopping Permit User Sessions...
iun 07 21:18:57 Alex-Laptop systemd[1]: systemd-user-sessions.service: Deactivated successfully.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped Permit User Sessions.
iun 07 21:18:57 Alex-Laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped target Network.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped target Remote File Systems.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopping Network Manager...
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopping WPA supplicant...
iun 07 21:18:57 Alex-Laptop kernel: audit: type=1131 audit(1654625937.116:129): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:18:57 Alex-Laptop systemd[1]: wpa_supplicant.service: Deactivated successfully.
iun 07 21:18:57 Alex-Laptop systemd[1]: Stopped WPA supplicant.
iun 07 21:18:57 Alex-Laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:18:57 Alex-Laptop kernel: audit: type=1131 audit(1654625937.119:130): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
iun 07 21:19:57 Alex-Laptop systemd[1]: avahi-daemon.service: Processes still around after final SIGKILL. Entering failed mode.
iun 07 21:19:57 Alex-Laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
iun 07 21:19:57 Alex-Laptop systemd[1]: avahi-daemon.service: Failed with result 'timeout'.
iun 07 21:19:57 Alex-Laptop systemd[1]: avahi-daemon.service: Unit process 368 (avahi-daemon) remains running after unit stopped.
iun 07 21:19:57 Alex-Laptop systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
iun 07 21:19:57 Alex-Laptop kernel: audit: type=1131 audit(1654625997.343:131): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
iun 07 21:20:27 Alex-Laptop systemd[1]: NetworkManager.service: State 'stop-sigterm' timed out. Killing.
iun 07 21:20:27 Alex-Laptop systemd[1]: NetworkManager.service: Killing process 400 (NetworkManager) with signal SIGKILL.
iun 07 21:21:57 Alex-Laptop systemd[1]: NetworkManager.service: Processes still around after SIGKILL. Ignoring.
iun 07 21:23:27 Alex-Laptop systemd[1]: NetworkManager.service: State 'final-sigterm' timed out. Killing.
iun 07 21:23:27 Alex-Laptop systemd[1]: NetworkManager.service: Killing process 400 (NetworkManager) with signal SIGKILL.