Public bug reported: On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version).
After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached). I then tried init=/lib/systemd/systemd in grub without quiet and splash and found that it was blocking on "a start job is running for Create Volatile files and directories". A search on the internet later, I found that the problem was solved by this approach : http://forums.debian.net/viewtopic.php?f=10&t=118008 So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works! While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?) This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dpkg.log" https://bugs.launchpad.net/bugs/1392637/+attachment/4260400/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392637 Title: Cannot boot with newly installed systemd if /tmp/ is filled with files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
