There seems to be a rather widespread live-image regression since 2009-10-10.
Could you please look at bug 448495. I think it is the same. Mario, can you start dbus, hal and gdm by hand as described in bug 448495? Do you think it is the same bug?
I am seeing this a lot in /var/log/syslog:
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: avahi-daemon 0.6.25 starting up.
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: WARNING: Failed to contact D-Bus daemon.
Oct 12 05:59:50 ubuntu init: avahi-daemon main process (1451) terminated with status 255
Oct 12 05:59:50 ubuntu init: avahi-daemon main process ended, respawning
There seems to be a rather widespread live-image regression since 2009-10-10.
Could you please look at bug 448495. I think it is the same. Mario, can you start dbus, hal and gdm by hand as described in bug 448495? Do you think it is the same bug?
I am seeing this a lot in /var/log/syslog:
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: avahi-daemon 0.6.25 starting up. get_private( ): Failed to connect to socket /var/run/ dbus/system_ bus_socket: No such file or directory
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: dbus_bus_
Oct 12 05:59:50 ubuntu avahi-daemon[1451]: WARNING: Failed to contact D-Bus daemon.
Oct 12 05:59:50 ubuntu init: avahi-daemon main process (1451) terminated with status 255
Oct 12 05:59:50 ubuntu init: avahi-daemon main process ended, respawning
also gdm, hal and ubiquity terminating a lot.