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

dino99 1313271 at bugs.launchpad.net
Wed May 7 15:35:33 UTC 2014


New feedback after rebooting with 'systemd'

Booted with 3.15 kernel without issue that time; so that problem seems
to be fixed now.

oem at dev32:~$ systemctl list-units --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.

oem at dev32:~$ systemctl list-units-files
Unknown operation 'list-units-files'.

That is, so the previous failing D-Bus connection error is not seen if
systemd is used for booting.

** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

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



More information about the foundations-bugs mailing list