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 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 Status in snapd: Invalid Status in systemd package in Ubuntu: Invalid Status in systemd source package in Trusty: Fix Committed Bug description: [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] * On boot, /run/nologin should not exist * Logins should not be prevented [Regression Potential] * This impacts systems with snapd and deputy systemd only (not the default configuration) [Original Descriptions] I've installed snapd on an up-to-date Ubuntu 14.04 server system running LTS enablement kernel. After toying with snapd and some simple snaps I logged out (so far everything was OK). I returned to the console after a while (I'm not sure if I logged out but I suspect I had to) and I saw the login prompt. After entering my username a line was printed "System is booting up" and I was kicked back ot the login prompt (It never asked for my password). After rebooting the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
