From owner-freebsd-current@FreeBSD.ORG Tue Apr 7 04:18:51 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FF0D10656E8; Tue, 7 Apr 2009 04:18:51 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2F4C98FC19; Tue, 7 Apr 2009 04:18:50 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n374IoY9091110; Mon, 6 Apr 2009 21:18:50 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id scu8g949hnewfq7ncjafvz4kn6; Mon, 06 Apr 2009 21:18:50 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49DAD429.6090309@freebsd.org> Date: Mon, 06 Apr 2009 21:18:49 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090404 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Robert Noland 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> In-Reply-To: <1239077210.1908.39.camel@balrog.2hip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: KDE4 and input events stalled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Apr 2009 04:18:51 -0000 >>>> * 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