From owner-freebsd-bugs Mon Feb 10 17:57:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA02772 for bugs-outgoing; Mon, 10 Feb 1997 17:57:49 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02758 for ; Mon, 10 Feb 1997 17:57:25 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.5/8.8.5) id MAA03008; Tue, 11 Feb 1997 12:56:49 +1100 (EST) Message-ID: <19970211125647.01074@usn.blaze.net.au> Date: Tue, 11 Feb 1997 12:56:47 +1100 From: David Nugent To: Zach Heilig Cc: Mark Murray , freebsd-bugs@freebsd.org Subject: Re: moused and X11R6 References: <199702101852.UAA04203@grackle.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <199702101852.UAA04203@grackle.grondar.za>; from Mark Murray on Feb 02, 1997 at 08:52:53PM Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 02, 1997 at 08:52:53PM, Mark Murray wrote: > Zach Heilig wrote: > > I'm pretty sure I tracked down my problem. moused & X are working > > together nicely again. The problem seemed to be that I had typed: > > > > vidcontrol -m on > > > > in the virtual terminal that was later used to run X. Ah, nice to know. The chances of this happening on most installations would be small though, assuming that X is starting up on the first inactive vt, no? > > Problems went away after I thought of that and turned it off... > > That is a bug in itself; the fact that it messes up X. I would be a > sod to fix, though. Couldn't the X server simply force it off on its when it starts up? #include . . { struct mouse_info mouse; mouse.operation = MOUSE_HIDE; ioctl(0, CONS_MOUSECTL, &mouse); } Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/