touch-packages team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

Fairly sure, without actually reproducing myself, that "telinit u" is
starting a fresh systemd and taking over PID1, instead of either calling
back to upstart (the current PID1) or doing nothing, either of which
would be preferable.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

-- 
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:
  switching init systems together with a libc upgrade kills X and
  disrupts the upgrade

Status in systemd package in Ubuntu:
  In Progress

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.

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