@krake, hopefully, one of the undermentioned demonstrates this:
rpm -qa | Select-String -Pattern '-nm|NetworkManager' NetworkManager-libnm-1.52.0-1.fc42.x86_64 NetworkManager-1.52.0-1.fc42.x86_64 NetworkManager-openvpn-1.12.0-3.fc42.x86_64 NetworkManager-team-1.52.0-1.fc42.x86_64 NetworkManager-wwan-1.52.0-1.fc42.x86_64 NetworkManager-wifi-1.52.0-1.fc42.x86_64 NetworkManager-l2tp-1.20.20-2.fc42.x86_64 NetworkManager-libreswan-1.2.24-2.fc42.x86_64 NetworkManager-pptp-1.2.12-9.fc42.x86_64 NetworkManager-openconnect-1.2.10-7.fc42.x86_64 NetworkManager-libreswan-gnome-1.2.24-2.fc42.x86_64 NetworkManager-ppp-1.52.0-1.fc42.x86_64 NetworkManager-bluetooth-1.52.0-1.fc42.x86_64 NetworkManager-adsl-1.52.0-1.fc42.x86_64 NetworkManager-config-connectivity-fedora-1.52.0-1.fc42.noarch NetworkManager-libnm-1.52.0-1.fc42.i686 NetworkManager-vpnc-1.4.0-3.fc42.x86_64 kf6-networkmanager-qt-6.15.0-1.fc42.x86_64 plasma-nm-6.4.1-1.fc42.x86_64 plasma-nm-l2tp-6.4.1-1.fc42.x86_64 plasma-nm-openconnect-6.4.1-1.fc42.x86_64 plasma-nm-openswan-6.4.1-1.fc42.x86_64 plasma-nm-openvpn-6.4.1-1.fc42.x86_64 plasma-nm-pptp-6.4.1-1.fc42.x86_64 plasma-nm-vpnc-6.4.1-1.fc42.x86_64
It appears to reproduce regardless, for the undermentioned occurs upon activating the hotspot on a reboot:
Additionally, it now (I don’t think this was true beforehand) doesn’t appear when connected to a Wi-Fi network:
I remember experiencing this > 3 years ago on an old laptop that I still have, and expecting that it was due to its aged hardware. However, on a Framework 16? It can’t have that poor of a Wi-Fi chip!


