Date: Mon, 06 Apr 2009 21:18:49 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Robert Noland <rnoland@freebsd.org> Cc: current@freebsd.org Subject: Re: KDE4 and input events stalled Message-ID: <49DAD429.6090309@freebsd.org> In-Reply-To: <1239077210.1908.39.camel@balrog.2hip.net> References: <49DA752B.5030805@freebsd.org> <934e1d760904061438k7d70d683re5c9d9a29e311942@mail.gmail.com> <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239057809.1908.2.camel@balrog.2hip.net> <49DAC742.8090507@freebsd.org> <1239075455.1908.36.camel@balrog.2hip.net> <49DACDBD.3030809@freebsd.org> <1239077210.1908.39.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>> * If I start kdm from /etc/ttys, I get a blank >>>> screen on startup. If I start it from a root >>>> login, it works okay for the first login. >>> This sounds more like it is waiting on hal/dbus to start up than >>> anything. > > So, basically X should wait on hal/dbus t become ready. Looking at the code, this might be impossible. /usr/local/etc/rc.d/hal does some very strange gyrations to delay its own start until after at least one getty process has started. That would make it highly improbable that hal can start before X if X is being started from /etc/ttys. I'm not familiar enough with hal to know why it might want to do this. Any ideas? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DAD429.6090309>