https://bugzilla.novell.com/show_bug.cgi?id=331002#c18 Martin Wilck <martin.wilck@fujitsu-siemens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|martin.wilck@fujitsu-siemens.com | --- Comment #18 from Martin Wilck <martin.wilck@fujitsu-siemens.com> 2007-10-25 03:07:12 MST --- With the proposal from bug 333735, comment #12, it was ok for me in ~20 subsequent boots. It's not a clean solution though. Solution proposal: a) remove <fork/> directive in /etc/dbus-1/system.conf b) use "startproc -s" to start dbus in /etc/init.d/dbus, like this: startproc -s -f -p $DBUS_DAEMON_PID $DBUS_DAEMON_BIN This has the same affect as <fork/>, but now startproc is aware of the fact dbus detaches and waits until dbus is initialized (verified that by means of my "gdm" error message). The current approach (with <fork/>) is broken, because there is no means to make sure that dbus is up when other services depending on dbus start. The problem would be more obvious if the haldaemon and consolekit rc scripts failed obviously when dbus isn't functional. Currently the rc scripts pretend to have succeeded, but later the service is marked "unused". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.