[Bug 521407] Re: dbus does not start after reboot. stale files in /var/run/dbus/
Alexander List
521407 at bugs.launchpad.net
Mon May 7 17:42:40 UTC 2012
*** This bug is a duplicate of bug 950662 ***
https://bugs.launchpad.net/bugs/950662
** This bug is no longer a duplicate of bug 856810
Boot hangs at "Booting system without full network configuration..."
** This bug has been marked a duplicate of bug 950662
Waiting for network message on bootup when all network devices are up
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/521407
Title:
dbus does not start after reboot. stale files in /var/run/dbus/
Status in “dbus” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: dbus
I recently upgraded one Ubuntu box from Gutsy or Hardy to Jaunty.
DBus no longer starts at boot. This has two major symptoms:
* The avahi daemon no longer starts, hence it's not possible to SSH in using a ".local" hostname (bug 519917).
* GDM starts, but the X server doesn't respond to keyboard or mouse input. Ctrl+Alt+F1 to log in at the console also doesn't do anything.
My workaround so far is to SSH in from another computer (using a
fully-qualified hostname or IP address) and execute "/etc/init.d/dbus
start ; /etc/init.d/gdm restart". That sequence runs fine and solves
the issues, until reboot.
# apt-cache policy dbus
dbus:
Instalados: 1.2.12-0ubuntu2.1
Candidato: 1.2.12-0ubuntu2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/521407/+subscriptions
More information about the foundations-bugs
mailing list