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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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

Reply via email to