[Bug 1908012] Re: System did not boot anymore after broken cable

2021-03-05 Thread Launchpad Bug Tracker
[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bind9 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 T

Re: [Bug 1908012] Re: System did not boot anymore after broken cable

2021-01-04 Thread BertN45
Sorry, that is not the same!! I'm connected to a router and a router does give me the IP address, a bridge does not provide you with an IP address, so the system will react differently. As you should have noticed from my description, it goes wrong trying to get a web address resolved after having

[Bug 1908012] Re: System did not boot anymore after broken cable

2021-01-04 Thread Christian Ehrhardt 
Thank you for your explanations BertN45, I've taken a VM and tried to replicate your scenario by keeping it connected to a bridge, but that bridge not connected anywhere else). That should match your case - but Ubuntu Server as well as Ubuntu Desktop guests started well in my case. So either it

[Bug 1908012] Re: System did not boot anymore after broken cable

2020-12-17 Thread BertN45
I detected the problem, due to a hardware error, which has been handled extremely badly. I will explain it very simple: I have a normal network connection with my local network, but the connection to the Internet is missing. Ubuntu boots, but after login the system gets into a loop and only displ

[Bug 1908012] Re: System did not boot anymore after broken cable

2020-12-16 Thread Lucas Kanashiro
Thank you for taking the time to file a bug report. Checking the attached logs the only thing I can see is your 'sh.desktop' failing many times and some errors from the gnome-shell. I do not think they are related to the problem you have. Moreover, what you described does not help a developer to r