@wlraider70 This seems not to be directly related. Same as #16 by @Michael Heuberger.
The issue of this thread is about this message: invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind. It can not find the initscript and thus is not able to execute it. Whereas your message... invoke-rc.d: initscript systemd-logind, action "start" failed. ...indicates that the initscript was in fact executed, but did fail (even though it's strange that "Job is already running" produces a fail. On my system (14.04) it does not produce an error when I run "invoke- rc.d systemd-logind start" as root, while it is already running). Maybe this thread helps (specifically #4): "invoke-rc.d: initscript systemd-logind, action "start" failed." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1320563 Btw. I was also surprised at not being able to edit comments. I guess it's because the posts end up in a mailing list. e.g. http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg4504011.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325142 Title: failure to update libpam-systemd in 14.04 due to missing logind init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
