*** This bug is a duplicate of bug 858122 ***
https://bugs.launchpad.net/bugs/858122
@daemonrebel:
The following worked for me (borrowed from post #9):
You need to
(i) create directories /run and /run/lock,
(ii) move contents of /var/run into /run and /var/lock into /run/lock,
(iii) delete directories /var/run and /var/lock
(iv) create replacement simlinks; e.g. 'ln -s /run /var/run' and 'ln -s
/run/lock /var/lock'
If you've never messed too much with Linux, it will be a little tricky.
I booted w/o recovery console (it gets stuck in read only mode for me
sometimes). Once you get to point where it's hanging and failing to boot
further, hit ctrl-alt-F1. This will bring you to a virtual terminal. Log
in as root or as a sudoer (you should be one). Attempt to move all the
contents of the folders as described, like:
mkdir /run
mv /var/run/* /run]
etc.
If there is anything in these folders you cannot move or delete, it's
possible it is a special mount point file. If rm <file> fails, try
umount -fl <file> then attempt rm <file> again. After you move all of
the contents, create the symlinks, reboot, and you should be okay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811441
Title:
Unable to connect to the system bus: Failed to connect to socket
/var/run/dbus/system_bus_socket: Connection refused (oneiric)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/811441/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
