[SOLVED] no wifi in first minutes after boot

bgme · 2025-07-13 17:50:10

Today I meet the problems that NetworkManager can't connect to the wifi with ecrypted password for a period of time after system boot and report no secrets: No agents were available for this request.

When I couldn't connect to the network, I checked with KWalletManager to make sure kwallet was working properly. I also tried rebooting, but the problem persists.

Here is a simple timeline:

18:06:46 start boot
18:07:02 log in succeed
18:07:04 unlock kwallet
18:10:49 NetworkManager report org.kde.plasma.networkmanagement agent registered

During from 18:07:04 to 18:10:49, I unable to connect to wifi.

Jul 13 18:06:46 archlinux kernel: Linux version 6.15.6-arch1-1 (linux@archlinux) (gcc (GCC) 15.1.1 20250425, GNU ld (GNU Binutils) 2.44.0) #1 SMP PREEMPT_DYNAMIC Thu, 10 Jul 2025 17:10:18 +0000
Jul 13 18:07:02 arch systemd[1229]: Queued start job for default target Main User Target.
Jul 13 18:07:04 arch systemd[1229]: Started Unlock kwallet from pam credentials.
Jul 13 18:10:49 arch NetworkManager[4151]: <info>  [1752401449.1976] agent-manager: agent[0a30711767e77b7c,:1.46/org.kde.plasma.networkmanagement/1000]: agent registered

I has checked Backgroud Services and make sure the Plasma Network Management module is enabled.

--------------------------------------------

Environment:

DE: KDE Plasma 6.4.2
WM: KWin (Wayland)
WM Theme: Breeze
networkmanager version 1.52.1

--------------------------------------------

Logs:

the part log of NetworkManager.service

# journalctl -u NetworkManager
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3088] manager: NetworkManager state is now DISCONNECTED
Jul 13 18:10:36 arch NetworkManager[4151]: <warn>  [1752401436.3089] device (wlp1s0): Activation: failed for connection 'LL'
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3091] device (wlp1s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3244] device (wlp1s0): set-hw-addr: set MAC address to 0E:11:3C:55:B3:18 (scanning)
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3663] device (wlp1s0): supplicant interface state: interface_disabled -> inactive
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3664] device (p2p-dev-wlp1s0): supplicant management interface state: interface_disabled -> inactive
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3664] device (wlp1s0): supplicant interface state: inactive -> interface_disabled
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3665] device (p2p-dev-wlp1s0): supplicant management interface state: inactive -> interface_disabled
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3712] device (wlp1s0): supplicant interface state: interface_disabled -> inactive
Jul 13 18:10:36 arch NetworkManager[4151]: <info>  [1752401436.3712] device (p2p-dev-wlp1s0): supplicant management interface state: interface_disabled -> inactive
Jul 13 18:10:38 arch NetworkManager[4151]: <info>  [1752401438.9879] device (wlp1s0): Activation: starting connection 'LL' (83819006-e8e0-4551-950c-c02893650876)
Jul 13 18:10:38 arch NetworkManager[4151]: <info>  [1752401438.9880] audit: op="connection-activate" uuid="83819006-e8e0-4551-950c-c02893650876" name="LL" pid=1579 uid=1000 result="success"
Jul 13 18:10:38 arch NetworkManager[4151]: <info>  [1752401438.9881] device (wlp1s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 13 18:10:38 arch NetworkManager[4151]: <info>  [1752401438.9883] manager: NetworkManager state is now CONNECTING
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0031] device (wlp1s0): set-hw-addr: set-cloned MAC address to A6:4C:41:AF:AF:48 (random)
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0453] device (wlp1s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0454] device (wlp1s0): Activation: (wifi) access point 'LL' has security, but secrets are required.
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0454] device (wlp1s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0457] device (wlp1s0): supplicant interface state: inactive -> interface_disabled
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0457] device (p2p-dev-wlp1s0): supplicant management interface state: inactive -> interface_disabled
Jul 13 18:10:39 arch NetworkManager[4151]: <warn>  [1752401439.0458] device (wlp1s0): no secrets: No agents were available for this request.
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0459] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets', managed-type: 'full')
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0460] manager: NetworkManager state is now DISCONNECTED
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.0663] device (wlp1s0): set-hw-addr: set MAC address to B2:0B:95:5E:3F:D1 (scanning)
Jul 13 18:10:39 arch NetworkManager[4151]: <warn>  [1752401439.1095] device (wlp1s0): Activation: failed for connection 'LL'
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1097] device (wlp1s0): supplicant interface state: interface_disabled -> inactive
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1097] device (p2p-dev-wlp1s0): supplicant management interface state: interface_disabled -> inactive
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1097] device (wlp1s0): supplicant interface state: inactive -> interface_disabled
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1098] device (p2p-dev-wlp1s0): supplicant management interface state: inactive -> interface_disabled
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1100] device (wlp1s0): supplicant interface state: interface_disabled -> inactive
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1100] device (p2p-dev-wlp1s0): supplicant management interface state: interface_disabled -> inactive
Jul 13 18:10:39 arch NetworkManager[4151]: <info>  [1752401439.1103] device (wlp1s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 13 18:10:49 arch NetworkManager[4151]: <info>  [1752401449.1976] agent-manager: agent[0a30711767e77b7c,:1.46/org.kde.plasma.networkmanagement/1000]: agent registered
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.4831] policy: auto-activating connection 'LL' (83819006-e8e0-4551-950c-c02893650876)
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.4836] device (wlp1s0): Activation: starting connection 'LL' (83819006-e8e0-4551-950c-c02893650876)
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.4837] device (wlp1s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.4839] manager: NetworkManager state is now CONNECTING
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5055] device (wlp1s0): set-hw-addr: set-cloned MAC address to A6:2F:EA:58:A8:CE (random)
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5477] device (wlp1s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5478] device (wlp1s0): Activation: (wifi) access point 'LL' has security, but secrets are required.
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5478] device (wlp1s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5481] device (wlp1s0): supplicant interface state: inactive -> interface_disabled
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5481] device (p2p-dev-wlp1s0): supplicant management interface state: inactive -> interface_disabled
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5595] device (wlp1s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5597] device (wlp1s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 13 18:10:51 arch NetworkManager[4151]: <info>  [1752401451.5599] device (wlp1s0): Activation: (wifi) connection 'LL' has security, and secrets exist.  No new secrets needed.

the part log of kwallet

$ journalctl --user -g kwallet
-- Boot e3d2e23f7445453f818b4cc118673705 --
Jul 13 18:07:03 arch sddm-helper[1261]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jul 13 18:07:04 arch systemd[1229]: Started Unlock kwallet from pam credentials.
Jul 13 18:07:12 arch systemd[1229]: Created slice Slice /app/dbus-:1.2-org.kde.kwalletd6.
Jul 13 18:07:12 arch systemd[1229]: Started dbus-:1.2-org.kde.kwalletd6@0.service.
Jul 13 18:07:19 arch systemd[1229]: Created slice Slice /app/dbus-:1.2-org.kde.kwalletmanager.
Jul 13 18:07:19 arch systemd[1229]: Started dbus-:1.2-org.kde.kwalletmanager@0.service.

Last edited by bgme (2025-07-15 10:13:50)

seth · 2025-07-13 20:22:18

18:06:46 start boot
18:07:02 log in succeed
18:07:04 unlock kwallet
===> Jul 13 18:10:39 arch NetworkManager[4151]: <warn> [1752401439.0458] device (wlp1s0): no secrets: No agents were available for this request.
18:10:49 NetworkManager report org.kde.plasma.networkmanagement agent registered

So no big surprises there and the only question is what takes org.kde.plasma.networkmanagement so long.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

bgme · 2025-07-14 00:10:27

@seth

The complete system journal (very very long):
https://0x0.st/8krW.txt

seth · 2025-07-14 08:40:03

Indeed it is
Most of it is however spam from beesd and sing-box.
Incidentally, all those early starting, network depending services might be the only thing slowing down plasma so much (there're no glaring errors, everything just takes time)
Have you considered https://wiki.archlinux.org/title/Networ … et_on_boot ?

bgme · 2025-07-14 10:37:25

seth wrote:

Incidentally, all those early starting, network depending services might be the only thing slowing down plasma so much (there're no glaring errors, everything just takes time)

I agree with you.

Today, I tested it again.

First time, store wifi password encrypted and reboot. The network is stuck for a long time as described above.

When network is stuck, I noticed the backgroud services, not only Plasma Network Management module, are all not running.

And the tray on right bottom work abnormally too. Some of application, such as goldendict, are running, but not displayed on tray.

-------------------

Second time, store wifi password not encrypted and reboot. Everything is normal.

Open Backgroud Services as soon as I log in and all services are running.

-------------------

Do you know how to debug this problems?

seth · 2025-07-14 13:26:21

What I meant is stuff like syncthing, beesd, sing-box, nebula and dnscrypt-proxy that clearly depends on functional network but starts way before NM has established a connection and then complains about it.
There's also keepassx, which starts ahead of kwallet.
Basically trim down the system to the bare minimum, then start re-adding elements until the start of the org.kde.plasma.networkmanagement gets delayed again. There's your offender.

bgme · 2025-07-14 15:47:16

After several rounds of testing, I finally found the offender.

$ systemctl --user cat rclone-mount.service   
# /home/arch/.config/systemd/user/rclone-mount.service
[Unit]
Description=Rclone mount Service
After=network-online.target

[Service]
Type=simple
Restart=on-failure
RestartSec=5s
ExecStart=/usr/bin/rclone mount wasabi:bgme-public-files /home/arch/wasabi

[Install]
WantedBy=default.target

I don't know why, but once enable this service the problem will occur.

seth · 2025-07-14 15:59:11

https://wiki.archlinux.org/title/Networ … ait-online
These targets are all (networkd isn't any better) nonsense anyway (network-online is reached once all devices are configured, it doesn't mean you've an active route to some desired host)
=> wrap "/usr/bin/rclone mount wasabi:bgme-public-files /home/arch/wasabi" in some script that does sth. like

ping -c1 -w120 relevant.host && /usr/bin/rclone mount wasabi:bgme-public-files /home/arch/wasabi || logger "wasabi rclone failed, host not up in 2 minutes"

bgme · 2025-07-15 03:08:13

Thanks for you advice.

Is the topic title length have limit? I try to edit the topic to add [SOLVED] to title but failed.

seth · 2025-07-15 06:47:44

Is the topic title length have limit?

Yup, sorry - just shorten the the subject a bit ("[SOLVED] no wifi in first minutes after boot" or so)

Arch Linux

#1 2025-07-13 17:50:10

[SOLVED] no wifi in first minutes after boot

#2 2025-07-13 20:22:18

Re: [SOLVED] no wifi in first minutes after boot

#3 2025-07-14 00:10:27

Re: [SOLVED] no wifi in first minutes after boot

#4 2025-07-14 08:40:03

Re: [SOLVED] no wifi in first minutes after boot

#5 2025-07-14 10:37:25

Re: [SOLVED] no wifi in first minutes after boot

#6 2025-07-14 13:26:21

Re: [SOLVED] no wifi in first minutes after boot

#7 2025-07-14 15:47:16

Re: [SOLVED] no wifi in first minutes after boot

#8 2025-07-14 15:59:11

Re: [SOLVED] no wifi in first minutes after boot

#9 2025-07-15 03:08:13

Re: [SOLVED] no wifi in first minutes after boot

#10 2025-07-15 06:47:44

Re: [SOLVED] no wifi in first minutes after boot

Board footer