Date: Tue, 25 Jun 1996 11:09:25 +1000 (EST) From: David Dawes <dawes@rf900.physics.usyd.edu.au> To: sos@freebsd.org Cc: current@freebsd.org Subject: Re: moused conflicts with X11 Message-ID: <199606250109.LAA02494@rf900.physics.usyd.edu.au> In-Reply-To: <199606241104.NAA06679@ra.dkuug.dk> from "sos@freebsd.org" at Jun 24, 96 01:04:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
>> > 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 :( That isn't true for the XFree86 servers. They close the mouse device when switching away from the X server. They do this so that other things can use the mouse (eg, an X server running on another vty). David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606250109.LAA02494>