touch-packages team mailing list archive

[Launchpad Bug Tracker <1430479@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 219-4ubuntu5

---------------
systemd (219-4ubuntu5) vivid; urgency=medium

  * Merge from experimental branch:
    - /lib/lsb/init-functions.d/40-systemd: Don't ignore systemd unit
      dependencies in "degraded" mode. (LP: #1429734)
    - rules-ubuntu/71-power-switch-proliant.rules: Add support for HP ProLiant
      m400 Server Cartridge soft powerdown on Linux 3.16. (LP: #1428811)
  * systemctl: Don't forward telinit u to upstart. This works around upstart's
    Restart() always reexec'ing /sbin/init on Restart(), even if that changes
    to point to systemd during the upgrade. This avoids running systemd during
    a dist-upgrade. (LP: #1430479)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Wed, 11 Mar 2015 11:01:36 +0100

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  "telinit u" under upstart (upstart's Restart command) with systemd-
  sysv installed runs systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  I've today had two machines kill my X session during dist-upgrade, and
  it happened during libc6 postinst. Dmesg shows that systemd got
  somehow started during the earlier phase of the upgrade. X logs show a
  failure with "(EE) Cannot establish any listening sockets" etc..

  Adam can fill in the more detailed analysis of what's happening
  there.. but I think it should be fairly easy to reproduce by
  installing vivid from an earlier image and dist-upgrading to current,
  if needed.

  Reproducer:
   - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic)
   - Switch apt sources to vivid
   - sudo apt install systemd-sysv
   - sudo telinit u  # systemd command, forwards to upstart's /lib/sysvinit/telinit
   - Or directly: sudo /lib/sysvinit/telinit u

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+subscriptions