← Back to team overview

touch-packages team mailing list archive

[Bug 1430479] Re: switching init systems together with a libc upgrade kills X and disrupts the upgrade

 

Debugging notes:

 - Running telinit u on a current vivid system under upstart, but with
systemd-sysv installed (i. e. select upstart from grub, using
init=/sbin/upstart) is returning immediately. strace shows that it's
connecting to the upstart socket. dmesg shows that
upstart-{udev,file}-bridge restarts and otherwise not much is going on.

 - Running systemctl daemon-reexec on that system fails immediately with
"Failed to get D-Bus connection: Operation not permitted" as the systemd
D-Bus socket isn't available.

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


References