You are not logged in.

#1 2021-10-12 01:23:00

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

WiFi taking 4 seconds to connect on login

Hi, it's me again. I've been dual booting Arch+KDE with Kubuntu 21.04 to test the PRIME sync issue, and i've noticed that, on Kubuntu, WiFi comes instantly when i login (after SDDM), whereas on Arch it takes like 4 seconds. On that time i have noticed that my WiFi appears as disconnected, then it spins and connects to the network.

systemd-analyze blame
19.225s NetworkManager-wait-online.service
  415ms dev-mapper-akroasis.device
  129ms systemd-udev-trigger.service
  127ms upower.service
  126ms udisks2.service
   99ms mnt-games.mount
   85ms boot-EFI.mount
   80ms systemd-rfkill.service
   79ms user@1000.service
   77ms plymouth-deactivate.service
   77ms plymouth-quit-wait.service
   76ms plymouth-quit.service
   60ms systemd-journal-flush.service
   58ms systemd-udevd.service
   56ms polkit.service
   49ms smb.service
   43ms systemd-tmpfiles-clean.service
   41ms systemd-journald.service
   38ms NetworkManager.service
   38ms lvm2-monitor.service
   32ms avahi-daemon.service
   32ms systemd-logind.service
   28ms systemd-tmpfiles-setup.service
   25ms systemd-fsck@dev-disk-by\x2duuid-caf9a274\x2d35b4\x2d4897\x2d85e3\x2da9b1141735d9.service
   21ms nmb.service
   20ms systemd-fsck@dev-disk-by\x2duuid-8936\x2d4088.service
   16ms plymouth-start.service
   15ms systemd-tmpfiles-setup-dev.service
   14ms systemd-vconsole-setup.service
   12ms systemd-binfmt.service
   12ms systemd-backlight@backlight:amdgpu_bl0.service
   12ms plymouth-read-write.service
   10ms wpa_supplicant.service
   10ms dev-hugepages.mount
    9ms bluetooth.service
    9ms dev-mqueue.mount
    9ms sys-kernel-debug.mount
    9ms sys-kernel-tracing.mount
    9ms modprobe@fuse.service
    8ms tmp.mount
    7ms kmod-static-nodes.service
    7ms modprobe@configfs.service
    6ms modprobe@drm.service
    6ms user-runtime-dir@1000.service
    6ms systemd-modules-load.service
    6ms systemd-remount-fs.service
    5ms systemd-random-seed.service
    4ms systemd-update-utmp.service
    4ms boot.mount
    3ms systemd-sysctl.service
    3ms systemd-user-sessions.service
    3ms rtkit-daemon.service
    3ms sys-fs-fuse-connections.mount
    2ms systemd-backlight@leds:platform::kbd_backlight.service
    2ms proc-sys-fs-binfmt_misc.mount
    2ms sys-kernel-config.mount
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @19.868s
└─multi-user.target @19.868s
  └─smb.service @19.818s +49ms
    └─nmb.service @19.795s +21ms
      └─network-online.target @19.794s
        └─NetworkManager-wait-online.service @568ms +19.225s
          └─NetworkManager.service @529ms +38ms
            └─dbus.service @525ms
              └─basic.target @524ms
                └─sockets.target @524ms
                  └─dbus.socket @524ms
                    └─sysinit.target @523ms
                      └─systemd-backlight@leds:platform::kbd_backlight.service @585ms +2ms
                        └─system-systemd\x2dbacklight.slice @331ms
                          └─system.slice @141ms
                            └─-.slice @141ms

If you need something more, please ask for it. Thanks!

Last edited by Vektor_98 (2021-10-12 01:23:27)

Offline

#2 2021-10-12 07:04:48

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,007

Re: WiFi taking 4 seconds to connect on login

If you've configured your wifi within KDE and have a password, an attempt at a connection can only be made after KDE's kwallet has been unlocked which can only happen once you've finished logging in. It's possible Kubuntu has some post-login script that either forces a immediate rescan for networks (... nmcli wifi rescan) or you've set up the connection as a "system connection " ("make this connection available to all users" in KDE's plasma-nm dialog) which will lead to the wifi password being stored by NM itself (unencrypted in a root only readable dir) but meaning that NM doesn't have to wait for you to log in and can actually initialize the connection as soon as it finds the network.

Last edited by V1del (2021-10-12 07:14:45)

Offline

#3 2021-10-12 19:05:04

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

Re: WiFi taking 4 seconds to connect on login

V1del wrote:

If you've configured your wifi within KDE and have a password, an attempt at a connection can only be made after KDE's kwallet has been unlocked which can only happen once you've finished logging in. It's possible Kubuntu has some post-login script that either forces a immediate rescan for networks (... nmcli wifi rescan) or you've set up the connection as a "system connection " ("make this connection available to all users" in KDE's plasma-nm dialog) which will lead to the wifi password being stored by NM itself (unencrypted in a root only readable dir) but meaning that NM doesn't have to wait for you to log in and can actually initialize the connection as soon as it finds the network.

Thanks V1del! I'll look it up on my laptop as soon as i get back from work. I think i have some space left to restore my dual boot and check what kind of magic does Kubuntu in that regard. Thans for the help. Will update the post with the proper answer when i solve this

Offline

#4 2021-10-12 22:37:33

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

Re: WiFi taking 4 seconds to connect on login

Update: I still haven't check Kubuntu. but i noted that on Arch, my WiFi device won't show up until 2 seconds after login, then it takes 1 second more to connect.

Offline

#5 2021-10-13 06:08:47

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,007

Re: WiFi taking 4 seconds to connect on login

Which all sounds pretty normal given the limitations I mentioned, is that really that big of a deal? What are you starting in those 4 seconds that this is an actual hindering annoyance?

Offline

#6 2021-10-13 15:03:21

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

Re: WiFi taking 4 seconds to connect on login

V1del wrote:

Which all sounds pretty normal given the limitations I mentioned, is that really that big of a deal? What are you starting in those 4 seconds that this is an actual hindering annoyance?

Hello agaon V1del, i can say that is an issue with NetworkManager. I have a custom script that works on login and it fails if it does not detect the connection on login. Today i tried stopping NetworkManager.service and restarting it, and there i observed that it takes said amount of time to enable the connection. Kubuntu does not have said issue.
Here are the logs from NetworkManager manually stopping and starting the service (Arch)

Oct 13 12:00:48 blackfuture systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 13 12:00:48 blackfuture audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:00:48 blackfuture kernel: audit: type=1131 audit(1634137248.121:229): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:01:12 blackfuture dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.100' (uid=0 pid=2963 comm="/usr/bin/NetworkManager --no-daemon ")
Oct 13 12:01:12 blackfuture audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:01:12 blackfuture kernel: audit: type=1130 audit(1634137272.923:239): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:01:13 blackfuture NetworkManager[2963]: <info>  [1634137273.5268] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 13 12:01:14 blackfuture dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.104' (uid=0 pid=3063 comm="sudo journalctl -b NetworkManager ")
Oct 13 12:01:14 blackfuture sudo[3063]:   vektor : TTY=pts/1 ; PWD=/home/vektor ; USER=root ; COMMAND=/usr/bin/journalctl -b NetworkManager
Oct 13 12:01:23 blackfuture systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 13 12:01:23 blackfuture audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:01:23 blackfuture kernel: audit: type=1131 audit(1634137283.131:250): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:03 blackfuture polkit-kde-authentication-agent-1[1288]: Message of action:  "Authentication is required to stop 'NetworkManager.service'."
Oct 13 12:02:06 blackfuture polkitd[1113]: Operator of unix-session:2 successfully authenticated as unix-user:vektor to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.108 [systemctl stop NetworkManager] (owned by unix-user:vektor)
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2463] caught SIGTERM, shutting down normally.
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2476] device (wlp4s0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2478] manager: NetworkManager state is now DISCONNECTING
Oct 13 12:02:06 blackfuture dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.100' (uid=0 pid=2963 comm="/usr/bin/NetworkManager --no-daemon ")
Oct 13 12:02:06 blackfuture audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2590] device (wlp4s0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
Oct 13 12:02:06 blackfuture kernel: audit: type=1130 audit(1634137326.256:258): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2850] dhcp4 (wlp4s0): canceled DHCP transaction
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.2851] dhcp4 (wlp4s0): state changed bound -> terminated
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.3226] manager: NetworkManager state is now DISCONNECTED
Oct 13 12:02:06 blackfuture NetworkManager[2963]: <info>  [1634137326.3301] exiting (success)
Oct 13 12:02:06 blackfuture systemd[1]: NetworkManager.service: Deactivated successfully.
Oct 13 12:02:06 blackfuture audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:06 blackfuture kernel: audit: type=1131 audit(1634137326.330:259): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:11 blackfuture polkit-kde-authentication-agent-1[1288]: Message of action:  "Authentication is required to start 'NetworkManager.service'."
Oct 13 12:02:14 blackfuture polkitd[1113]: Operator of unix-session:2 successfully authenticated as unix-user:vektor to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.113 [systemctl start NetworkManager] (owned by unix-user:vektor)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0254] NetworkManager (version 1.32.12-1) is starting... (after a restart)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0254] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0265] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 13 12:02:14 blackfuture audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:14 blackfuture kernel: audit: type=1130 audit(1634137334.024:262): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:14 blackfuture kdeconnectd[1317]: propsReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture DiscoverNotifier[1326]: propsReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture kded5[1225]: propsReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture kdeconnectd[1317]: nmReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture DiscoverNotifier[1326]: nmReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture kded5[1225]: nmReply "Object does not exist at path “/org/freedesktop/NetworkManager”"
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0298] manager[0x5601822e1040]: monitoring kernel firmware directory '/lib/firmware'.
Oct 13 12:02:14 blackfuture dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.116' (uid=0 pid=3139 comm="/usr/bin/NetworkManager --no-daemon ")
Oct 13 12:02:14 blackfuture kded5[1225]: QObject::connect: No such signal org::freedesktop::NetworkManager::StateChanged(uint)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0917] hostname: hostname: using hostnamed
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0918] hostname: hostname changed from (none) to "blackfuture"
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0919] dns-mgr[0x56018229b250]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0931] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/ieee80211/phy0/rfkill2) (driver rtw_8822ce)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0933] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0944] manager[0x5601822e1040]: rfkill: Wi-Fi hardware radio set enabled
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0945] manager[0x5601822e1040]: rfkill: WWAN hardware radio set enabled
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0986] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-bluetooth.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0989] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-wwan.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0992] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-ovs.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0995] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-adsl.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.0998] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-wifi.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1036] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.32.12-1/libnm-device-plugin-team.so)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1038] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1039] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1039] manager: Networking is enabled by state file
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1040] dhcp-init: Using DHCP client 'internal'
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1040] settings: Loaded settings plugin: keyfile (internal)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1065] device (lo): carrier: link connected
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1069] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1079] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1088] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1097] device (wlp4s0): driver supports Access Point (AP) mode
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1100] manager: (wlp4s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.1103] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.3289] device (wlp4s0): set-hw-addr: set MAC address to 3A:38:0E:F2:6B:28 (scanning)
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.5509] ovsdb: Could not connect: No such file or directory
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.5510] ovsdb: disconnected from ovsdb
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.5559] agent-manager: agent[67a0f324c0c2392b,:1.27/org.kde.plasma.networkmanagement/1000]: agent registered
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.5804] device (wlp4s0): supplicant interface state: internal-starting -> disconnected
Oct 13 12:02:14 blackfuture NetworkManager[3139]: <info>  [1634137334.5805] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 13 12:02:16 blackfuture systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 13 12:02:16 blackfuture audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:16 blackfuture kernel: audit: type=1131 audit(1634137336.124:267): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.6392] policy: auto-activating connection 'Fibertel WiFi443 5.8GHz' (206d1b7a-844f-4178-a24f-dc00d4473997)
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.6398] device (wlp4s0): Activation: starting connection 'Fibertel WiFi443 5.8GHz' (206d1b7a-844f-4178-a24f-dc00d4473997)
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.6400] device (wlp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.6402] manager: NetworkManager state is now CONNECTING
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.6410] device (wlp4s0): set-hw-addr: reset MAC address to 30:C9:AB:DF:14:1F (preserve)
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8576] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8579] device (wlp4s0): Activation: (wifi) access point 'Fibertel WiFi443 5.8GHz' has security, but secrets are required.
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8580] device (wlp4s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8581] sup-iface[9548754c760a34e3,2,wlp4s0]: wps: type pbc start...
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8605] device (wlp4s0): supplicant interface state: disconnected -> interface_disabled
Oct 13 12:02:18 blackfuture kded5[1225]: plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/4"
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8760] device (wlp4s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8762] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] device (wlp4s0): Activation: (wifi) connection 'Fibertel WiFi443 5.8GHz' has security, and secrets exist.  No new secrets needed.
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] Config: added 'ssid' value 'Fibertel WiFi443 5.8GHz'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] Config: added 'scan_ssid' value '1'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8764] Config: added 'psk' value '<hidden>'
Oct 13 12:02:18 blackfuture NetworkManager[3139]: <info>  [1634137338.8954] device (wlp4s0): supplicant interface state: interface_disabled -> inactive
Oct 13 12:02:19 blackfuture NetworkManager[3139]: <info>  [1634137339.1097] device (wlp4s0): supplicant interface state: inactive -> scanning
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.0572] device (wlp4s0): supplicant interface state: scanning -> authenticating
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.0612] device (wlp4s0): supplicant interface state: authenticating -> associating
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.0690] device (wlp4s0): supplicant interface state: associating -> associated
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.0814] device (wlp4s0): supplicant interface state: associated -> 4way_handshake
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1194] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1195] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Fibertel WiFi443 5.8GHz"
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1197] device (wlp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1201] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1548] dhcp4 (wlp4s0): state changed unknown -> bound, address=192.168.0.207
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1556] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:23 blackfuture dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.116' (uid=0 pid=3139 comm="/usr/bin/NetworkManager --no-daemon ")
Oct 13 12:02:23 blackfuture audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1660] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1662] device (wlp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 13 12:02:23 blackfuture kernel: audit: type=1130 audit(1634137343.164:268): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1667] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1670] manager: NetworkManager state is now CONNECTED_SITE
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1670] policy: set 'Fibertel WiFi443 5.8GHz' (wlp4s0) as default for IPv4 routing and DNS
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1673] device (wlp4s0): Activation: successful, device activated.
Oct 13 12:02:23 blackfuture NetworkManager[3139]: <info>  [1634137343.1676] manager: startup complete

Last edited by Vektor_98 (2021-10-13 15:03:44)

Offline

#7 2021-10-13 15:28:44

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,007

Re: WiFi taking 4 seconds to connect on login

Post a comparison log from Kubuntu. What we definitely see here is that is indeed relying on plasma-nm to provide the connection secrets.

Offline

#8 2021-10-13 15:56:50

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

Re: WiFi taking 4 seconds to connect on login

V1del wrote:

Post a comparison log from Kubuntu. What we definitely see here is that is indeed relying on plasma-nm to provide the connection secrets.

Sorry, the other one was not correct.
Here is one from Arch since boot time (from turning on the laptop up to fully functional desktop)
https://gist.github.com/CygnusTerminal/ … 464f2b0e7d
And the one from Kubuntu
https://gist.github.com/CygnusTerminal/ … 5d6c721226
Forgot to mention, both Kubuntu and Arch are set to use the "All users may connect to this network" option on the test WiFi network.

Last edited by Vektor_98 (2021-10-13 16:01:35)

Offline

#9 2021-10-13 16:20:41

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,007

Re: WiFi taking 4 seconds to connect on login

Mhm, but at least from this, the reason is as I suspected, your Arch NM waits for plasma-nm to give it the secret (hence this can only happen after you log in) and your Ubuntu NM connects as it can use them before you even logged in.

Not sure how plasma handles the allow all user setting, but have you also selected the "save password for all users" under the security tab? That will at the least also be necessary. Maybe also check your /etc/NetworkManager/system-connections/ with a root shell on both, both should contain a file including a PSK for this to work like you'd expect.

Last edited by V1del (2021-10-13 16:25:32)

Offline

#10 2021-10-13 17:49:42

Vektor_98
Member
Registered: 2021-04-03
Posts: 23

Re: WiFi taking 4 seconds to connect on login

V1del wrote:

Mhm, but at least from this, the reason is as I suspected, your Arch NM waits for plasma-nm to give it the secret (hence this can only happen after you log in) and your Ubuntu NM connects as it can use them before you even logged in.

Not sure how plasma handles the allow all user setting, but have you also selected the "save password for all users" under the security tab? That will at the least also be necessary. Maybe also check your /etc/NetworkManager/system-connections/ with a root shell on both, both should contain a file including a PSK for this to work like you'd expect.

Hmm, interesting,

ls -a

on both Kubuntu and Arch only show the ".nmconnection" files, no psk or other type of files. I'll test the security thing. Will reboot and see how it fares. Thanks!

Offline

Board footer

Powered by FluxBB