From owner-freebsd-bugs  Sun Mar  9 06:40:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA23986
          for bugs-outgoing; Sun, 9 Mar 1997 06:40:03 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA23970;
          Sun, 9 Mar 1997 06:40:01 -0800 (PST)
Date: Sun, 9 Mar 1997 06:40:01 -0800 (PST)
Message-Id: <199703091440.GAA23970@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Adam David <adam@veda.is>
Subject: Re: i386/2924: syscons X keyboard gets stuck in capsmode
Reply-To: Adam David <adam@veda.is>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR i386/2924; it has been noted by GNATS.

From: Adam David <adam@veda.is>
To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA)
Cc: FreeBSD-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: i386/2924: syscons X keyboard gets stuck in capsmode
Date: Sun, 9 Mar 1997 14:52:20 +0000 (GMT)

 > >	Sometimes, entering '@' from the keyboard in X causes the keyboard to
 > >	get stuck in capsmode (ShiftLock?). Pressing CapsLock will then toggle
 > >	the LED, but does not change the capslock status. 
 > 
 > Would you tell us the keymap you load for syscons, and the keyboard
 > section of XF86Config, specifically XkbXXX settings?
 
 Standard syscons keymap, since dead accents are not yet supported.
 
 Section	"Keyboard"
     Protocol    "Standard"
     AutoRepeat  500 5
     LeftAlt     Meta
     RightAlt    ModeShift
 EndSection
 
 I am not defining any XkbXXX settings.
 
 > >	Define "keycode 11 = 2 quotedbl 2 at" with xmodmap.
 > >	In normal use, press RALT+RSHIFT+2 to type '@'.
 > >	Random, probably related to debounce timings.
 
 > Do you remember since which revision your problem started? There WAS a
 > change to clear shift/lock key flags, but that code is supposed to be
 > executed only DURING vty switching (between vtys or X and a vty). Not
 > while in a vty.
 
 I have only seen this problem since the recent changes. I do not remember when
 it actually started, it is not something that became immediately apparent.
 Perhaps it is related to the kbdio changes rather than the vty switching?
 However, switching vty back and forth does restore the correct mode setting.
 
 Adam