I read the startup log using "journalctl -xe" (attached, in case anyone wants to check it out).
It seemed D-Bus, among other things, failed to start with result 'dependency'.
Turns out /var/run was not being (properly?) mounted.
systemd[1]: var-run.mount failed to run 'mount' task (...)
All I had to do was comment the following line from /etc/fstab and it solved the problem:
/var/run tmpfs size=3M,noatime 0 0
It was likely me who added that to fstab in the past, and I realize now that had the same problem on my laptop, except instead of trying to fix it and understand why, I reinstalled the whole system in a rush.
Joolz, try to check the startup log ("journalctl -xe" ) to see what's going on. I don't think this will be the cause, since it's a fresh install, but you may find some info there.
Hope this helps anyone having the same problem.
Cheers.
I read the startup log using "journalctl -xe" (attached, in case anyone wants to check it out).
It seemed D-Bus, among other things, failed to start with result 'dependency'.
Turns out /var/run was not being (properly?) mounted.
systemd[1]: var-run.mount failed to run 'mount' task (...)
I found this solution, which is exactly for my case (after upgrade): c0rp.kz/ ubuntu- boot-problem- after-upgrade- 14-10-15- 04/
http://
All I had to do was comment the following line from /etc/fstab and it solved the problem:
/var/run tmpfs size=3M,noatime 0 0
It was likely me who added that to fstab in the past, and I realize now that had the same problem on my laptop, except instead of trying to fix it and understand why, I reinstalled the whole system in a rush.
Joolz, try to check the startup log ("journalctl -xe" ) to see what's going on. I don't think this will be the cause, since it's a fresh install, but you may find some info there.
Hope this helps anyone having the same problem.
Cheers.