I had thought I attached a log file to this bug as per the instructions. Sorry if that was not sufficient.
Here is how to reproduce the bug: 1) Start with a new Ubuntu server install with a wifi card, connected to the internet though wifi. 2) Add or remove physical hardware from the machine, such that the hardware name of the wifi changes (for example, the name may change from wlp8s0 to wlp9s0 due to the hardware change). Maybe there are other ways the hardware name of a device can be changed. I'm no expert. For me, the thing that changed the name of the wifi device was installing an NVIDIA RTX 3090 graphics card into a system that previously did not have a graphics card, and was using the integrated graphics of the CPU/motherboard. 3) Due to the name of of the wifi hardware changing, the internet stops working. This happens because the file /etc/netplan/50-cloud-init.yaml had the wifi hardware name hardcoded as wlp8s0. When the name of the wifi hardware changed to wlp9s0, the file /etc/netplan/50-cloud- init.yaml did not update, so it couldn't find my wifi hardware anymore (even though the hardware was still working fine, the drivers were working fine, everything was fine except that the name had changed). 4) If you now go into the file /etc/netplan/50-cloud-init.yaml and edit it to update to the new hardware name wlp9s0, then everything will work again. The bug stems from the fact that there is a name hardcoded into /etc/netplan/50-cloud-init.yaml and that name can change. To fix the bug, there must be some way for /etc/netplan/50-cloud-init.yaml to refer to the wifi hardware in a way that will be consistent across hardware installs and changes to the system that will change the name of the network device. Apparently, in Linux, you can't just set this name once on install and expect it to be the same forever. I am just a user reporting a bug. I don't understand the system that I am trying to describe here. I don't know how Linux works, I don't know how /etc/netplan/50-cloud-init.yaml works, I don't understand the internals of your system. I am just a user reporting a bug. All I can do is report this bug and give you information to the best of my ability. I followed the instructions and uploaded the log file. I'm sorry if the log file is not sufficient. The instructions were followed to the best of my ability. Possibly I messed up and didn't follow the instructions correctly. Possibly the instructions are incomplete and following the instructions fails to give you the information you need to fix the bug. Possibly I could have written all the above steps in the first place instead of vaguely alluding to the name change and the file where the name had been hardcoded. I am consistently frustrated by issues with Linux just failing for no apparent reason and there being no way to fix the issue without endless internet searching and debugging. I desperately want Linux to work out of the box and not have issues like this. What can I say. I want you to fix this bug and I want to help you fix this bug. I can only do so much. Sorry if this isn't enough. This bug took me two hours to get my system working again. So that sucks that this bug exists, probably other people encountered this bug and didn't report it and spent time trying to fix it. If not for ChatGPT it would have taken me longer to fix the bug or I would have given up and installed Windows. Bugs happen, I understand, it's hard to get things perfect, I'm just trying to help in a very small way. Sorry for the rant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111774 Title: Installing a new graphics card causes wifi device to be renamed from wlp8s0 to wlp9s0 which breaks the internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2111774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
