[Bug 1313271] Re: [systemd] boot stopped at 'authenticate and authorize users...'

[Nik.Th.]

Yes, in order to boot and debugging systemd (reporting bugs..etc) you
must boot with systemd as PID 1, or else you will get similar errors.

It you have decided to participate in systemd testing, you should boot
the PC always with systemd as PID 1.

I think we can mark this bug as 'invalid', in order to keep the developers focused on other bugs. 
If you agree mark it as such. 

Regards

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1313271

Title:
  [systemd] boot stopped at 'authenticate and authorize users...'

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Utopic upgraded from Trusty i386 (fully upgraded: systemd
  2O4.8ubuntu1)

  The boot process goes well until:

  started login service
  started avahi mdns/dns-sd stack
  starting authenticate and authorize users to run privileged tasks ....

  then nothing happen, no errors/warnings, only waiting for something it
  cant find.

  That system is a single desktop with no lan/wan nor other users, only
  myself alone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1313271/+subscriptions