Date: Tue, 7 Apr 2009 16:11:46 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Robert Noland <rnoland@freebsd.org> Cc: Joe Marcus Clarke <marcus@freebsd.org>, current@freebsd.org Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) Message-ID: <92cd2ff70904071611r61c895b7g6517a99b286989a0@mail.gmail.com> In-Reply-To: <1239131313.1947.18.camel@balrog.2hip.net> References: <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239075455.1908.36.camel@balrog.2hip.net> <49DACDBD.3030809@freebsd.org> <1239077210.1908.39.camel@balrog.2hip.net> <49DAD429.6090309@freebsd.org> <1239078081.1908.41.camel@balrog.2hip.net> <49DAE987.7090802@freebsd.org> <1239086408.35025.59.camel@shumai.marcuscom.com> <20090407185915.GY31409@albert.catwhisker.org> <1239131313.1947.18.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I tweaked dependencies to force xdm to come up after hald, but even so, > > that didn't help much: it seems that hald isn't really ready to provide > > the services asked of it immediately. > The message "Starting hald" is misleading. Hald doesn't actually start until much, much later. > X will start up, register with dbus and ask for info from hald. If hald > isn't up, or ready it will loop for a bit, waiting. Once hald is up and > registers with dbus it will proceed. At least that is my recollection > of how the code worked. > I waited 15 minutes; screen still dead. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92cd2ff70904071611r61c895b7g6517a99b286989a0>