From owner-freebsd-questions Sat Jan 23 00:56:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03375 for freebsd-questions-outgoing; Sat, 23 Jan 1999 00:56:10 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from modgud.nordicdms.com (h21-168-107.nordicdms.com [207.21.168.107]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA03370 for ; Sat, 23 Jan 1999 00:56:09 -0800 (PST) (envelope-from walton@nordicdms.com) Received: (qmail 27819 invoked by alias); 22 Jan 1999 21:49:17 -0000 Message-ID: <19990122214917.27818.qmail@modgud.nordicdms.com> Received: (qmail 27805 invoked from network); 22 Jan 1999 21:49:16 -0000 Received: from mail-ftp.nordicdms.com (HELO mail-ftp) (207.21.168.100) by mail.nordicdms.com with SMTP; 22 Jan 1999 21:49:16 -0000 From: "Dave Walton" Organization: Nordic Entertainment Worldwide To: questions@FreeBSD.ORG, Date: Fri, 22 Jan 1999 13:49:15 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Keyboard freezes under 2.2.8. Reply-to: walton@nordicdms.com X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 22, 1999 at 08:19:28PM -0530, K. Arun said: > > On Wed, Jan 20, 1999 at 02:48:28PM -0800, Dave Walton said: > > It is ttyv3, and it does have `off' in the status column. > > => If X is running on a tty that is enabled, the conflict will cause > => exactly the problem you describe. (I learned that the hard way this > => morning...) > > What I do not understand is that the problem takes some time to > surface. If it were a problem with the X server, one wouldn't expect it to > start up properly, would one ? The freeze generally happens ten > minutes after starting up X. It is generally a consequence of a rapid > mouse clicks or simultaneous use of the keyboard and mouse. Is this > an X bug, one that has been reported ? Well, I don't know what one would expect, but I do know that what you describe is exactly what happens when X is using an enabled tty. But that appears to not be the problem in your case, so I'm not sure what's going on. Perhaps someone else here has any ideas? Dave ---------------------------------------------------------------------- Dave Walton Webmaster, Postmaster Nordic Entertainment Worldwide walton@nordicdms.com http://www.nordicdms.com ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message