** 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] + + * 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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660573 Title: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
