This bug was fixed in the package systemd - 204-5ubuntu20.24
---
systemd (204-5ubuntu20.24) trusty; urgency=medium
[ Thomas Voß ]
* Do not create /run/nologin, and thus make sure deputy systemd does not
prevent system logins. LP: #1660573.
systemd (204-5ubuntu20.23) trusty;
installing systemd 204-5ubuntu20.22, on pure trusty machine does result
in /run/nologin file being created. (WRONG)
installing systemd 204-5ubuntu20.24 does not result in /run/nologin file
being created. (GREAT)
** Tags removed: verification-needed
** Tags added: verification-done
--
You
Hello Zygmunt, or anyone else affected,
Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.24 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: systemd (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting up" while
** Changed in: systemd (Ubuntu Trusty)
Milestone: None => trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting up" while
** Description changed:
+ [Impact]
+
+ * Deputy systemd sometimes wrongly prevents TTY logins
+ * Since it is deputy systemd, it should not be controlling PAM stack nologin
feature, i.e. deputy systemd should not create /run/nologin since it's not
removing it reliably.
+
+ [Test Case]
+
+
Also no longer able to reproduce when installing systemd from tvoss's
PPA on a fresh VM (ubuntu-trusty-daily-amd64-server-20170131-disk1.img).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Trusty)
Status: New => Triaged
I've installed the updated systemd from tvoss' PPA and I didn't see
anything wrong anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is
I managed to reproduce the issue without snapd being involved at all.
Marking as invalid for snapd, bumping priority to "high". Among other
things, this blocks autopkgtests for snapd on trusty.
** Changed in: snapd
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
I did some digging into systemd-tmpfiles and its configuration. In the
trusty case, with systemd *not* running as PID 1, the systemd-tmpfiles
does not strictly need to create /run/nologin to shield state
transitions. For that, I removed creation of the file from trusty's
systemd-tmpfiles
I forgot to mention that pam_nologin prints "System is booting up." and
fails non-root logins when /var/run/nologin exists, which is why that is
relevant. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
With a freshly-booted up to date trusty VM (ubuntu-trusty-daily-
amd64-server-20170130-disk1.img, then dist-upgraded for libssl1.0.0
openssl), simply installing systemd seems to be sufficient to cause the
file to exist.
ubuntu@pjdc-test:~$ ls -l /var/run/nologin
ls: cannot access
what version of the systemd package do you have installed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting up" while trying to log in
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting up" while trying to log in after installing snapd
on ubuntu 14.04
** Changed in: snapd
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
I can occasionally reproduce the issue with an autopkgtest setup using a
qemu vm. Local spread tests using the qemu backend work fine, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug report against systemd seems relevant:
https://github.com/systemd/systemd/issues/3436
Other distributions are experiencing the issue, too:
https://bugzilla.opensuse.org/show_bug.cgi?id=980324
** Bug watch added: github.com/systemd/systemd/issues #3436
18 matches
Mail list logo
