*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My 15.10 "system" started to show quite similar symptoms today. Booting
with systemd the progress stops in the graphics 'ubuntu * * * * *'
displayed at the center of the screen. After maybe one minute the the
screen goes black and couple of lines are displayed proposing some
alternatives like to
Applied the patch successfully but failed to reboot with the same
symptoms, created journal1.txt please find attached herewith. On second
attempt systemd worked fine.
Pls note yesterday applied partial upgrade as well.
Thanks for the help.
> Date: Fri, 30 Oct 2015 09:25:01 +
> From:
Naz Ahmed [2015-10-31 8:30 -]:
> Applied the patch successfully but failed to reboot with the same
> symptoms, created journal1.txt please find attached herewith. On second
> attempt systemd worked fine.
It's expected that you need a reboot before things will actually work.
(If in doubt, do
This is further to my previous email;
Fourth and fifth attempts failed again with connection timeouts. Please
see journal2.txt.
Regards.
> Date: Sat, 31 Oct 2015 09:10:43 +
> From: martin.p...@ubuntu.com
> To: nazahme...@hotmail.com
> Subject: Re: [Bug 1509762] Re: services fail to start
- I did the PPA upgrade under upstart, then shutdown/restarted the
system, got connection timeouts, acquired terminal using Ctrl+Alt+F1,
created jounal1.txt.
- Attempted to boot the system with default systemd option successfully
and sent you the email with jornal1.txt file.
- Since then, I'm
Can you please enable this PPA and check whether boot is now working?
https://launchpad.net/~pitti/+archive/ubuntu/sru-test
This patch has worked for me, it definitively fixes the boot failure
with the exact same symptoms that you see; but I can't reproduce it on
225, just on (unpatched) 227; but
Ah, thanks! This looks like
https://github.com/systemd/systemd/issues/1505, a bug that's rather hard
to track down. I haven't seen it actually affecting version 225 as the
functionality that triggers this isn't used anywhere in the distro; but
you might have some third-party package installed
