Date: Fri, 27 Jul 2012 01:10:01 +0700 From: Erich Dollansky <erichfreebsdlist@ovitrap.com> To: Warren Block <wblock@wonkity.com> Cc: "Daniel P. Wright" <dani@dpwright.com>, freebsd-stable@freebsd.org Subject: Re: Keyboard cutting off soon after launching X Message-ID: <20120727011001.68e15c51@AMD620.ovitrap.com> In-Reply-To: <alpine.BSF.2.00.1207261057300.11518@wonkity.com> References: <CAP=piQc3HnetihuKkRpzC05BtAs-PM-eH9wvovrzdjVYbGf7Aw@mail.gmail.com> <alpine.BSF.2.00.1207260813300.10327@wonkity.com> <20120726215802.02dfbbcf@AMD620.ovitrap.com> <alpine.BSF.2.00.1207261057300.11518@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Jul 2012 11:03:05 -0600 (MDT) Hi, Warren Block <wblock@wonkity.com> wrote: > On Thu, 26 Jul 2012, Erich Dollansky wrote: > > > Enable moused in rc.conf and the following from xorg.conf helped me > > this time: > > > > Option "AllowEmptyInput" "false" # > The comment wrap there is very confusing. But please stop using > AllowEmptyInput. It was so misused that it has even been removed > from later versions of xorg. > http://www.wonkity.com/~wblock/docs/html/aei.html > I have read this before. But what else would you do when the line above solves the problem? > There is an interaction with hald and moused that makes it worthwhile > lately for some users to run moused from rc.conf. There may be a I wonder why. > similar interaction with kbdmux(4) or some other keyboard component > for keyboards. > > hald can be improved greatly by its absence. Isn't this the case on some Linux machines? Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120727011001.68e15c51>