Date: Mon, 06 Apr 2009 22:49:59 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Robert Noland <rnoland@freebsd.org> Cc: Joe Marcus Clarke <marcus@freebsd.org>, current@freebsd.org Subject: Hal and KDM breakage (was Re: KDE4 and input events stalled) Message-ID: <49DAE987.7090802@freebsd.org> In-Reply-To: <1239078081.1908.41.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> <49DAD429.6090309@freebsd.org> <1239078081.1908.41.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Noland wrote: > On Mon, 2009-04-06 at 21:18 -0700, Tim Kientzle wrote: >>>>>> * 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. Yep, that seems to be the issue. I got it to work finally by commenting out this one line from /usr/local/etc/rc.d/hald: #start_cmd="hald_start" In particular, this allows hald to startup in the regular sequence without that odd delay. Tim CCing marcus@; maybe he can explain why that delay was put in and whether ripping it back out makes sense.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DAE987.7090802>