From owner-freebsd-current  Mon Aug 12 16:23:55 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA08150
          for current-outgoing; Mon, 12 Aug 1996 16:23:55 -0700 (PDT)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA08135
          for <freebsd-current@FreeBSD.org>; Mon, 12 Aug 1996 16:23:52 -0700 (PDT)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA06517; Mon, 12 Aug 1996 16:23:21 -0700 (PDT)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
	id sma006515; Mon Aug 12 16:22:53 1996
Received: (from archie@localhost) by bubba.whistle.com (8.6.12/8.6.12) id QAA04171; Mon, 12 Aug 1996 16:22:52 -0700
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199608122322.QAA04171@bubba.whistle.com>
Subject: Re: locking up
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Mon, 12 Aug 1996 16:22:51 -0700 (PDT)
Cc: jlemon@americantv.com, freebsd-current@FreeBSD.org
In-Reply-To: <14324.839471898@time.cdrom.com> from "Jordan K. Hubbard" at Aug 7, 96 07:38:18 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


> > I have the same problem - I'm running 2.1.0R CD distribution, and at random
> > times during an X session, the keyboard just freezes up.  Executing 'kbd_mo
> '
> > doesn't fix the problem either.  Logging in remotely and killing the X serv
> > clears up the difficulty though, or executing the above commandline.
> 
> I never had this problem until I started using xmodmap with Xaccel to
> swap the caps lock and control keys on my new Microsoft natural
> keyboard (the Northgate I had before let me do this directly on the
> keyboard with a switch).
> 
> Now, every once in awhile (usually when I'm using the control key :-),
> the keyboard will lock up.  In the past I could clear it only by
> restartarting the X server, now it appears that this same gdb trick
> works for me in getting my keyboard back.  I've made a button for it
> in my fvwm menu. :-)
> 
> Still, it'd be nice to know how/why this trick rescues the keyboard
> for Xaccel.  Anyone see this same kind of problem with XFree86?

I get this a lot. It always happens when I'm pressing the CAPS LOCK key
at the same time as some other key. I HATE IT because I end up having to
kill about 30 vi sessions, etc., etc...

This is on 2.1.0-R with XFree86 S3 server.

By the way, after killing the X server, you can find the "lost" character
typed (the one that caused the hang) on the virtual console you started
X from (eg, at the login prompt)...

-Archie

___________________________________________________________________________
Archie L. Cobbs, archie@whistle.com  *  Whistle Communications Corporation