[Bug 1908012] Re: System did not boot anymore after broken cable
[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 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908012] Re: System did not boot anymore after broken cable
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 received my IP address from the router's DHCP. Note that I use TWO routers. the one closest to my desktop gives the IP address (router=192.168.1.1), but both need to be connected to get to the internet. The other one from the ISP has 192.168.0.1. The cable between both routers was broken. It is the configuration I did choose, to get wifi coverage in whole the house. Like I said I have done my part, there is nothing more I can do, since you do not seem to understand the issue. On Mon, 2021-01-04 at 11:30 +, Christian Ehrhardt wrote: > 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 must be something special (package installed, > configuration) in your failing Ubuntu systems OR your network issue > was more complex than just "connected to net, but not the internet". > Either way we'd need more details and tries on your end, since you > stated that you won#t come/reply back we are again at what Lucas > mentioned - a not actionable bug. > > Therefore I'm keeping it in incomplete state so that it can auto- > expire > if no further updates happen. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908012] Re: System did not boot anymore after broken cable
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 must be something special (package installed, configuration) in your failing Ubuntu systems OR your network issue was more complex than just "connected to net, but not the internet". Either way we'd need more details and tries on your end, since you stated that you won#t come/reply back we are again at what Lucas mentioned - a not actionable bug. Therefore I'm keeping it in incomplete state so that it can auto-expire if no further updates happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908012] Re: System did not boot anymore after broken cable
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 displays a purple or black screen. I did get the system out off the loop by disconnecting its Ethernet cable. This has been my solution till the cable had been repaired. Note that the solution only works for the HOST OS, my Ubuntu VBox VMs had the same problem and looped after login. Like I said the Windows VMs and the Fedora VM did not have that problem, because they handled this Internet missing issue correctly. As ex-OS designer, I solved many issues based on this type of information! I not familiar with the internal design of Linux, but I expect that Ubuntu tries to connect to the Internet after login for e.g livepatch or for a DNS server. In both cases the connection will fail and it looks like Ubuntu keeps trying in an endless loop, while blocking the desktop display function. I think the sh.desktop failing is the problem and it only got resolved after I pulled the Ethernet plug. I guess that sh.desktop needs an Internet function, that is not available. It returns an error and Ubuntu keeps trying for ever. If I pull the Ethernet plug, Ubuntu realizes, that it has to start anyhow. This is my last reaction to my bug-report, solve it or not. I don't care. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908012] Re: System did not boot anymore after broken cable
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 reproduce the problem and try to confirm/investigate the issue, so please try to describe how one could reproduce your issue. Due to that this bug is not actionable. Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: bind9 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
