Thanks. If you comment out this line from fstab: tmpfs /var/lock tmpfs defaults 0 0
do things work again? Note that this is really broken: /var/lock must be a symlink to /run/lock, otherwise different programs use different lock directories. However, it's not really obvious that this is the cause for it. Why did you add this entry, out of interest? ** Summary changed: - Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd + boot failure when mounting /var/lock as a tmpfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: boot failure when mounting /var/lock as a tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
