From owner-freebsd-x11@FreeBSD.ORG Mon Jan 4 17:12:17 2010 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39FB8106566B for ; Mon, 4 Jan 2010 17:12:17 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id E4ADF8FC15 for ; Mon, 4 Jan 2010 17:12:16 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o04HCGgu005289; Mon, 4 Jan 2010 10:12:16 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o04HCFC4005286; Mon, 4 Jan 2010 10:12:15 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 4 Jan 2010 10:12:15 -0700 (MST) From: Warren Block To: Zhang Weiwu In-Reply-To: <4B41B286.3010707@realss.com> Message-ID: References: <4B419C66.7090808@realss.com> <4B41A5A9.9040100@infracaninophile.co.uk> <4B41B286.3010707@realss.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Mon, 04 Jan 2010 10:12:16 -0700 (MST) Cc: freebsd-x11@freebsd.org Subject: Re: X take no mouse nor keyboard input X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2010 17:12:17 -0000 On Mon, 4 Jan 2010, Zhang Weiwu wrote: > Matthew Seaman ??: >> Sounds like dbus / hald breakage. Are those two daemons running? > No, none of them are running. I don't know I was expected to get them > running first. When I learn FreeBSD (5 years ago) such thing was not > mentioned in the handbook:) > > Should I start to read some new version of handbook on getting both running? >> >> What do you see in /var/log/Xorg.0.log ? > Ah, It says > > AllowEmptyInput is on... > > I don't know why I overlooked checking Xorg.0.log > > So the problem is "solved" by adding this to xorg.conf > > Section "ServerFlags" > Option "AllowEmptyInput" "False" > EndSection AllowEmptyInput is a source of problems and best avoided. If you want to manually configure keyboard and mouse in xorg.conf instead of letting hal/dbus do it, use Option "AutoAddDevices" "Off". Or rebuild xorg-server without hal support; it's a port option. -Warren Block * Rapid City, South Dakota USA