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

[dino99]

Despite my comment in #3 above, i've got hard time to boot with systemd today: the first two cold boots ended with some "failed" red warning while the system was loaded (too fast to be able to see about what was failing) then got X crashed.
So the error reported here was also seen by two times (before getting X crashing).
At first glance, i was blaming the new 'transitional' update-notifier, but without beeing sure about that. It seems either be :
- a boot race issue: system continue booting, while some mandatory driver/lib/service(s) still not ready.
- or the consequency of the rather rough method while previously shutting down the system: compared to upstart case, now the system seems to be really killed: looks like it have not the time to close/unload before shutting down. Wonder if it could be a valuable reason for the next cold boot to fail ?

-- 
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:
  Confirmed

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