Hi, On Tue, Oct 6, 2009 at 11:39 AM, Petter Reinholdtsen <p...@hungry.com>wrote:
> This ordering is correct as far as I know. hal starts before kdm, and > nothing starting after kdm should affect its behaviour. > > > Looking at the X log file, the log file from the failed startup > > stops where the working X log continues to process input devices > > from HAL. Although hal is started before kdm. Maybe it doesn't start > > fast enough? > > That might very well be the case. I suspect we might discover this > kind of problems more when we speed up the boot, ie latent race > conditions which have been hidden because the old boot was slow. > > Does it help to add a sleep command to the end of the hal script? For > the booting to work, hal need to be fully operational before its > init.d script exits, as the later scripts may expect hal to be > working. > I'll test that later this week. > > I suspect this bug should be about document the requirement of > enabling insserv, and that a new BTS report should be created to > adressed the failing kdm issue. > OK. Can you clone and retitle this bug, or should I file a new bug report? Regards, Rik
