Fedora 35 have to restart NetworkManager at login

Ask Fedora
1

Hello, with new Fedora 35 install I was able to connect to my Wifi without trouble, and reboots would subsequently let me login.

After dnf update it appears NetworkManager gets stuck forever trying to connect to my wifi.

I have to do sudo systemctl restart NetworkManager one or two times and it connects to wifi right away.

The following is the log output from journalctl when it’s having trouble:

Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2209] NetworkManager (version 1.32.12-1.fc35) is starting... (for the first time)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2211] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
Feb 16 12:30:59 fedora systemd[1]: Started Network Manager.
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2223] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2247] manager[0x55ccf8654040]: monitoring kernel firmware directory '/lib/firmware'.
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2264] hostname: hostname: using hostnamed
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2268] dns-mgr[0x55ccf862f250]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2279] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill2) (d>
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2282] manager[0x55ccf8654040]: rfkill: Wi-Fi hardware radio set enabled
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2282] manager[0x55ccf8654040]: rfkill: WWAN hardware radio set enabled
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2306] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-device-plugin-adsl.so)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2342] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-device-plugin-bluetooth.so)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2362] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-device-plugin-team.so)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2378] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-device-plugin-wifi.so)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2382] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-device-plugin-wwan.so)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2385] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2386] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2386] manager: Networking is enabled by state file
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2387] dhcp-init: Using DHCP client 'internal'
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2388] settings: Loaded settings plugin: keyfile (internal)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2403] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.32.12-1.fc35/libnm-settings-plugin-ifcfg-rh.s>
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2409] device (lo): carrier: link connected
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2412] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2421] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2438] settings: (enp0s31f6): created default wired connection 'Wired connection 1'
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.2443] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.4572] device (wlp2s0): driver supports Access Point (AP) mode
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.4584] manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.4592] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.7088] device (wlp2s0): set-hw-addr: set MAC address to 2E:4A:F0:73:BE:C7 (scanning)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9548] modem-manager: ModemManager available
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9895] device (wlp2s0): supplicant interface state: internal-starting -> disconnected
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9896] Wi-Fi P2P device controlled by interface wlp2s0 created
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9898] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9900] device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 12:30:59 fedora NetworkManager[964]: <info>  [1645032659.9905] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')fa
2

Would you like to try adding p2p_disabled=1 to /etc/wpa_supplicant/wpa_supplicant.conf file configuration then try to reboot your system and see if it working or not.

3

I tried that and rebooted. However, it still hangs on “Waiting for authorization” while connecting to wifi.

Restarting NetworkManager brings up the wifi connection right away.

4

Would you like to also share the systemctl status when NetworkManager works? May be we can find something there.

5

I’m sure you have it set but in settings is connect automatically and make available to other users checked.

6

The following is the status:

# systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-03-04 08:56:54 EST; 1h 28min ago
       Docs: man:NetworkManager(8)
   Main PID: 5140 (NetworkManager)
      Tasks: 3 (limit: 18829)
     Memory: 5.1M
        CPU: 1.043s
     CGroup: /system.slice/NetworkManager.service
             └─5140 /usr/sbin/NetworkManager --no-daemon

Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9399] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9399] device (wlp2s0): DHCPv4 lease renewal requested
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9452] dhcp4 (wlp2s0): canceled DHCP transaction
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9453] dhcp4 (wlp2s0): state changed bound -> terminated
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9457] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9600] device (wlp2s0): supplicant interface state: associated -> 4way_handshake
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9600] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9875] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
Mar 04 09:17:16 pythagoras NetworkManager[5140]: <info>  [1646403436.9885] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
Mar 04 09:17:20 pythagoras NetworkManager[5140]: <info>  [1646403440.0942] dhcp4 (wlp2s0): state changed unknown -> bound, address=10.6.6.69
7

Connect automatically was checked. However, “Available to all users” wasn’t checked, I marked it and rebooted it but same problem, unfortunately.

8

I tried some different scenarios to replicate your journalctl but my wifi still connect as usual. But there are different report I get from my system when restarting NetworkManager. On my system it will not ask for DHCP renewal.

If I create wifi connection, above option is enable by default. Since yours was not, may be there are other configuration that changed there too.

Would you like to try Gnome Settings → Wi-Fi, find the current wifi connection, click the gear icon and click “Forget Connection”. After that try to connect again to wifi and leave all the default settings.

9

I’m actually using KDE, I assume same instructions though?

10

Yes, maybe you want to try to forget the connection and try to connect it again and leave everything default.

11

Darn, forgetting it and starting over again didn’t solve the problem. I wonder what’s going on here? Is there any way to safely reinstall NetworkManager? That’s the only thing I can think of.

12

Yes, you could do that sudo dnf reinstall NetworkManager.

If after reinstalling NetworkManager the problem still come, would you like to post the result of systemctl list-unit-files --state=enabled | grep service.

13

Okay only question: If I do a reinstall with dnf…and I have no network to install NetworkManager, that might be bad?

14

It does the download before the reinstall. Thus if the network is working before you start it will not break during the reinstall. Any hardware configs in place are not interrupted by the reinstall. Only when the adapter is reconfigured by a restart/reboot or when done in some other manner.

15

Okay I tried dnf reinstall NetworkManager and it reinstalled. I rebooted, but same problem with wifi persists unless I restart NetworkManager. The services command lists the following:

abrt-oops.service                  enabled enabled
abrt-vmcore.service                enabled enabled
abrt-xorg.service                  enabled enabled
abrtd.service                      enabled enabled
accounts-daemon.service            enabled enabled
atd.service                        enabled enabled
auditd.service                     enabled enabled
avahi-daemon.service               enabled enabled
bluetooth.service                  enabled enabled
chronyd.service                    enabled enabled
crond.service                      enabled enabled
dbus-broker.service                enabled enabled
docker.service                     enabled disabled
falcon-sensor.service              enabled disabled
flatpak-add-fedora-repos.service   enabled enabled
getty@.service                     enabled enabled
gpd.service                        enabled disabled
import-state.service               enabled enabled
irqbalance.service                 enabled enabled
iscsi-onboot.service               enabled enabled
iscsi.service                      enabled enabled
lvm2-monitor.service               enabled enabled
mcelog.service                     enabled enabled
mdmonitor.service                  enabled enabled
ModemManager.service               enabled enabled
multipathd.service                 enabled enabled
NetworkManager-dispatcher.service  enabled enabled
NetworkManager-wait-online.service enabled enabled
NetworkManager.service             enabled enabled
nfs-convert.service                enabled disabled
nftables.service                   enabled disabled
ostree-remount.service             enabled enabled
power-profiles-daemon.service      enabled enabled
qemu-guest-agent.service           enabled enabled
rpmdb-rebuild.service              enabled enabled
rsyslog.service                    enabled enabled
rtkit-daemon.service               enabled enabled
sddm.service                       enabled enabled
selinux-autorelabel-mark.service   enabled enabled
smartd.service                     enabled enabled
sssd.service                       enabled enabled
systemd-homed-activate.service     enabled disabled
systemd-homed.service              enabled enabled
systemd-oomd.service               enabled enabled
systemd-pstore.service             enabled enabled
udisks2.service                    enabled enabled
upower.service                     enabled enabled
uresourced.service                 enabled enabled
vboxservice.service                enabled enabled
vgauthd.service                    enabled disabled
vmtoolsd.service                   enabled enabled
16

Hi, I’m out of idea. The services look ok for me. If I could find something you can try, I’ll let you know.

17

You can use:
sudo yum install yum-utils
and
sudo yumdownloader --resolve NetworkManager --installroot=/dep --releasever=/

to download rpms for offline usage. Then install the rpms like so after uninstalling NetworkManager

sudo dnf --disablerepo=* --skip-broken install /location/of/rpms/*.rpm

I do not know if --installroot=/dep is where the rpms go. It did not work when I tried it. They just got downloaded to /.

18

First I did a dnf upgrade to make sure I had the latest everything and rebooted.

So I did yumdownloader --resolve --alldeps NetworkManager after reading up on the other options, they weren’t necessary.

During uninstall process though it was trying to uninstall a ton of ‘unused’ packages, I saved the output to a text file just in case.

As a side step, I also renamed /etc/NetworkManager/system-connections as it was saving connection information.

I uninstalled NetworkManager and rebooted.

I installed the rpms in the dep folder I saved the rpms to, NetworkManager installed, and rebooted again.

After boot, I saw systemctl status NetworkManager was active and running, but in KDE there was absolutely no UI to get connected anymore.

I figured this was because ‘unused’ packages were removed, so I parsed the text file in another workstation and did yumdownloader with all deps for each package (thankfully downloaded rpms were skipped), then transferred those rpms to my laptop and did dnf install for everything.

This time on reboot the NetworkManager UI was present and allowed me to pick wifi, I entered password. However, once again it’s stuck on Waiting for Authorization and I had to restart NetworkManager twice to get connected.

Short of reinstalling the whole operating system, I’m at a loss and will just end up living with this nuisance. Thanks for the help anyway.