On 4 August 2014 14:22, Martin Pitt <martin.p...@ubuntu.com> wrote:
> Can you please attach your /etc/network/interfaces? At the time when it
> hangs, can you switch VTs and log in there already? Or ssh in? If you
> get access to the machine in that state, can you please get the output
> of "sudo systemctl status" and attach it here? Thanks!
>
My /etc/network/interfaces is just bare minimal:
auto lo
iface lo inet loopback
I can switch VTs but all of them simply have "_" blinking, and no
gettys spawned and cannot login.
No, I cannot ssh in as network-manager / wifi are not running yet.
However, symlinking networking unit to /dev/null allows me to boot
with systemd. It looks like "ifup -a" is hanging for me upon trying to
execute tinc ifup hooks. So I'll add that package to the bug report
and debug it later when I have time as to what's going on wrong with
tinc.
Or like add proper systemd unit generators to tinc VPNs =)
--
Regards,
Dimitri.
** Also affects: tinc (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- systemd boot hangs
+ systemd boot hangs -> sysv:networking -> ifup -> tinc
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1352334
Title:
systemd boot hangs -> sysv:networking -> ifup -> tinc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1352334/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
