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 configuration. Packages for testing purposes are in ppa :thomas-voss/trusty.
@Paul: Would be great if you could give the package a round of testing, too. -- 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: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: 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
