*** 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
I confirm the bug, which Laurent is experiencing.
After upgrading from natty to oneiric it seems, that dbus does not exit
cleanly upon shutdown/reboot. As a result /var/run/dbus/pid and
/var/run/dbus/system_bus_socket are present upon the next system boot,
which prevents dbus from starting up.
$
One possible workaround would be to remove the whole /var/run/dbus
before starting the dbus daemon. That could be done, for example, in the
dbus.conf file used by upstart (see the attached patch file).
** Patch added: dbus.conf.patch
The attachment dbus.conf.patch of this bug report has been identified
as being a patch. The ubuntu-reviewers team has been subscribed to the
bug report so that they can review the patch. In the event that this is
in fact not a patch you can resolve this situation by removing the tag
'patch' from
** Changed in: dbus (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521407
Title:
dbus does not start after reboot
To manage notifications about this bug go
I was recently affected by a similar bug after upgrading my system from
natty to oneiric.
My problem is also related to bug #508832 because my system already has
a /var/run/dbus/pid file when it starts, which prevents dbus from
starting up.
--
You received this bug notification because you are
I still have this problem. The workaround mentioned above does not
always work reliably; sometimes. However, restarting dbus when gdm is
stopped always works; although it also prints an asyncronous error-
message:
# /etc/init.d/gdm stop ; sleep 2 ; /etc/init.d/dbus st
op ; sleep 2 ;
