Date: Mon, 24 Jun 1996 13:04:18 +0200 (MET DST) From: sos@freebsd.org To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: current@freebsd.org (FreeBSD current) Subject: Re: moused conflicts with X11 Message-ID: <199606241104.NAA06679@ra.dkuug.dk> In-Reply-To: <199606241029.OAA00409@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jun 24, 96 02:29:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= who wrote:
>
> > Actually I think its an artifact from both moused & the X server
> > having /dev/mousedev open at the same time. This is only
> > fixable by either killing moused when running X, or have
> > moused track the shown vty, and open/close /dev/mousedev according
> > to that.
>
> Why? Syscons already detect when terminal video mode
> changed to graphics mode. All you need is turn off moused
> while syscons in graphics mode and turn it back on
> graphics mode exit.
Because the way I understand it, its because BOTH mosed & X has the
mousedevice open at the same time, this is only fixable by having
one of then close it. BUT the X server NEVER closes it during its
life time :(
However I might have another solution that also makes moused
unnessesary, more when I get to my home keyboard...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606241104.NAA06679>