hald seems to automatically spawn a console-kit-daemon instance if none is running, so if the consolekit init script is scheduled to start after hald, it will fail because the daemon is already running. Adding "use consolekit" or "after consolekit" to depend() in hald init script is enough to fix the problem.
sounds sensible for some reason it always starts before hald here but I guess this is pure luck.
(In reply to comment #1) > sounds sensible for some reason it always starts before hald here but I guess > this is pure luck. > Indeed. By chance consolekit was starting before hald on my box too, but the order changed when I added NetworkManager to the default runlevel, unveiling the missing dependency.
How about a "before hald" in consolekit? That way hal doesn't change for people who don't use consolekit.
(In reply to comment #3) > How about a "before hald" in consolekit? That way hal doesn't change for > people who don't use consolekit. > That would indicate that consolekit *needs* to be started before hald, but the situation is that hald *uses* consolekit. So IMO, "use consolekit" in hald would be better.
(In reply to comment #4) > (In reply to comment #3) > > How about a "before hald" in consolekit? That way hal doesn't change for > > people who don't use consolekit. > > > > That would indicate that consolekit *needs* to be started before hald, but the > situation is that hald *uses* consolekit. So IMO, "use consolekit" in hald > would be better. > Also, "use" doesn't add a hard dependency. It only says "if it's in the runlevel, hald could use it => start it before hald"
Fixed in hal-0.5.12_rc1-r2
