Confusion with wpa-supplicant

MetalInMyVeins · 2024-08-24 05:30:50

I'm unsure if this post should go in the networking section or here. Anyway, here's the relevant portion from my journalctl:
https://0x0.st/XywY.txt
As you can see, pacrunner.service is starting and terminating several times. Is this normal behavior? Cause during boot, at a point my screen gets flooded with `Started Proxy configuration daemon` which hasn't happened to me before.
Another thing is, I have always been using `wlp4s0` as network device, I don't know when it got changed to `wlan0`. Is this normal too?
And another thing is, after I do a fresh power-on, systemd (/sbin/init) consumes around 15% of CPU in average for several minutes. This doesn't happen when I restart the laptop. Is this normal too?

Last edited by MetalInMyVeins (2024-08-24 05:34:36)

seth · 2024-08-24 07:31:30

https://wiki.archlinux.org/title/Networ … face_names - installing iwd implies that.

The "journal" looks heavily edits, entries are ellided, lines doubled - I just it's also just a selection?
There isn't even an attempt covered to connect to a wireless AP, installing iwd and impicitly preventing the "predictable" interface name might have "broken" your NM config because it ignores wlan0 and doesn't configure wlp4s0 because that's no longer there?

MetalInMyVeins · 2024-08-25 12:59:28

I removed iwd and network device was changed back to wlp4s0. However the wpa-supplicant thing remains. Look at this portion of journalctl. Also, it has zero edits. I have just copied from terminal and pasted. What's causing this big number of pacrunner.service deactivation in a row? How can I fix it?
http://0x0.st/Xynd.txt

Last edited by MetalInMyVeins (2024-08-25 13:01:00)

seth · 2024-08-25 13:44:50

Don't copy out of the pager, it trunc>

The snippet doesn't involve a NM attempt to connect to a wifi AP at all until the very end

Aug 25 12:52:50 Archpad NetworkManager[788]: <info>  [1724568770.1204] manager: NetworkManager state is now CONNECTING

pacrunner is dbus activated, so something will try to active it - typically NM and specifically your proxy configuration there and likely it'll just hinge on a configured NIC.
So inspect your proxy settings and generally your NM configuration.

Arch Linux

#1 2024-08-24 05:30:50

Confusion with wpa-supplicant

#2 2024-08-24 07:31:30

Re: Confusion with wpa-supplicant

#3 2024-08-25 12:59:28

Re: Confusion with wpa-supplicant

#4 2024-08-25 13:44:50

Re: Confusion with wpa-supplicant

Board footer