From owner-freebsd-current  Mon Aug 12 21:16:07 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA15443
          for current-outgoing; Mon, 12 Aug 1996 21:16:07 -0700 (PDT)
Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA15435;
          Mon, 12 Aug 1996 21:16:05 -0700 (PDT)
Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) with ESMTP id VAA23940; Mon, 12 Aug 1996 21:14:30 -0700
From: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Message-Id: <199608130414.VAA23940@paris.CS.Berkeley.EDU>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: jlemon@americantv.com, freebsd-current@freebsd.org, sos@freebsd.org
Subject: Re: locking up 
In-reply-to: Your message of "Mon, 12 Aug 1996 19:52:49 PDT."
             <3451.839904769@time.cdrom.com> 
Date: Mon, 12 Aug 1996 21:14:29 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > 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.
> 
> Does the gdb trick work to get you out?  Looks like this is a bug in
> our console code then, and not the X server itself.
> 
> > 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)...
> 
> Yep!!!  Exact same symptoms here.  Oh Soooooooreeeeeen..  We have
> another nice little bug for you! :-)
> 
> 					Jordan

Hey yeah me too, cause I use caps-lock for my control key.  Three or four
times a day I'll have this happen.  I'm running XInside.

-josh