Public bug reported: See https://ubuntuforums.org/showthread.php?t=2502378 for more details.
Here are more details of the hardware configuration via System-Info Script https://paste.ubuntu.com/p/8WqxpZ9w6v/ With Ubuntu LTS 22 and 24 using any WiFi or Wired Network and changing the Identity Settings of Cloned Adress to "stable" breaks the NetworkManager. Up on connecting via GUI to the wired or WiFi Device, the devices shuts off leaving the Device lists in the Gnome GUI blank. I know thats just a brief description, but as soon as I edited the netplan file manually again and delete the macaddress: "stable" entry, it works again. Ive tried that with several wireless network configurations and the wired, and the permanent setting always cause this behaviour - so it atleast is depended to my hardware. The issue should be repeatable with that hardware at least by others. Maybe others will encounter it with different hardware configurations as well. If your user experience is that after a reboot no network connection is established automatically that was previously working to auto connect, and your wired/wifi list gets blank as soon as you connect to any selected together with visible "refreshes" of Gnomes GUI and optical glitches, as well as no lists of adapters or visible WiFi reappearing after that crash up to another reboot (or maybe until restarting services), than it may be likely you set the stable macaddress in some network and forgot about it - like me Instead of troubleshooting software and reinstalling networkmanager and its cfg, maybe check your netplan yaml files for any permanent setting. Quick help to find the corrupted file: grep -ri "macaddress" /etc/netplan/ or grep -ri "stable" /etc/netplan/ As I experienced this issue back in September, I got to admit I am not 100% sure if it was actually the "Stable" Setting or the "Permanent", as I tried both back and forward - but thats easy to test by anyone else for confirmation. If you can not repeat the issue I will can try it again. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-driver (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2089402 Title: NetworkManager breaks up on Macaddress: Stable aka "Cloned Adress: Stable" Status in network-manager package in Ubuntu: New Bug description: See https://ubuntuforums.org/showthread.php?t=2502378 for more details. Here are more details of the hardware configuration via System-Info Script https://paste.ubuntu.com/p/8WqxpZ9w6v/ With Ubuntu LTS 22 and 24 using any WiFi or Wired Network and changing the Identity Settings of Cloned Adress to "stable" breaks the NetworkManager. Up on connecting via GUI to the wired or WiFi Device, the devices shuts off leaving the Device lists in the Gnome GUI blank. I know thats just a brief description, but as soon as I edited the netplan file manually again and delete the macaddress: "stable" entry, it works again. Ive tried that with several wireless network configurations and the wired, and the permanent setting always cause this behaviour - so it atleast is depended to my hardware. The issue should be repeatable with that hardware at least by others. Maybe others will encounter it with different hardware configurations as well. If your user experience is that after a reboot no network connection is established automatically that was previously working to auto connect, and your wired/wifi list gets blank as soon as you connect to any selected together with visible "refreshes" of Gnomes GUI and optical glitches, as well as no lists of adapters or visible WiFi reappearing after that crash up to another reboot (or maybe until restarting services), than it may be likely you set the stable macaddress in some network and forgot about it - like me Instead of troubleshooting software and reinstalling networkmanager and its cfg, maybe check your netplan yaml files for any permanent setting. Quick help to find the corrupted file: grep -ri "macaddress" /etc/netplan/ or grep -ri "stable" /etc/netplan/ As I experienced this issue back in September, I got to admit I am not 100% sure if it was actually the "Stable" Setting or the "Permanent", as I tried both back and forward - but thats easy to test by anyone else for confirmation. If you can not repeat the issue I will can try it again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2089402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
