Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After upgrading to oneiric, Ubuntu appears to be unable to start dbus correctly, which virtually renders half the system unusable. The startup error seems to happen rather early in the bootstages - and I have not yet figured out where exactly, or even what actually causes it.

I've tried to run dbus manually (sudo service dbus start), but no avail. I'm really not sure what could be done.

What are my options? Do I have to reinstall Ubuntu (my /home is not going to be affected, as it's a partion)?

share|improve this question
up vote 1 down vote accepted

Read post #9 there:

share|improve this answer
Thank you, however, I have been able to fix it using this guide: - who would have thought that dbus would behave that way? :-( – hiobs Oct 15 '11 at 19:13

Boot up in single user mode (recovery mode and pick the "root shell" option from the menu) and do this:

mount -o remount,rw /
cd /var
rm -rf run lock
ln -s /run run
ln -s /run/lock lock

That is, change /var/run to a symlink pointing at /run and /var/lock to a symlink pointing at /run/lock. That's the new place they belong. You have to do it in single-user mode when services aren't running, however.

That's supposed to happen during the upgrade/install process, but there's a bug some encounter where it doesn't happen.

More details available behind here:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.