touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

** Description changed:

  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)
+  - Ensure that ubuntu-standard is installed
+  - Switch apt sources to vivid
+  - sudo apt install systemd-sysv libc6

** Description changed:

  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)
-  - Ensure that ubuntu-standard is installed
-  - Switch apt sources to vivid
-  - sudo apt install systemd-sysv libc6
+  - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic)
+  - Switch apt sources to vivid
+  - sudo apt install systemd-sysv libc6

** Description changed:

  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 libc6
+  - sudo apt install systemd-sysv
+  - sudo telinit u

** Summary changed:

- switching init systems together with a libc upgrade kills X and disrupts the upgrade
+ "telinit u" under upstart with systemd-sysv installed runs systemd

-- 
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 with systemd-sysv installed runs systemd

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.

  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

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