From adam@veda.is  Sun Mar  9 04:40:19 1997
Received: from veda.is (ubiq.veda.is [193.4.230.60])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA18755
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 Mar 1997 04:40:13 -0800 (PST)
Received: (from adam@localhost) by veda.is (8.8.4/8.7.3) id MAA15470; Sun, 9 Mar 1997 12:54:58 GMT
Message-Id: <199703091254.MAA15470@veda.is>
Date: Sun, 9 Mar 1997 12:54:58 GMT
From: Adam David <adam@veda.is>
Reply-To: adam@veda.is
To: FreeBSD-gnats-submit@freebsd.org
Subject: syscons X keyboard gets stuck in capsmode
X-Send-Pr-Version: 3.2

>Number:         2924
>Category:       i386
>Synopsis:       syscons X keyboard gets stuck in capsmode
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar  9 04:50:01 PST 1997
>Closed-Date:    Mon Mar 29 18:12:02 PST 1999
>Last-Modified:  Mon Mar 29 18:12:30 PST 1999
>Originator:     Adam David
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
Veda Internet
>Environment:

	syscons, XFree86 3.2, '@' on RALT+SHIFT+2 in xmodmap.

>Description:

	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. 

>How-To-Repeat:

	Define "keycode 11 = 2 quotedbl 2 at" with xmodmap.
	In normal use, press RALT+RSHIFT+2 to type '@'.
	Random, probably related to debounce timings.

>Fix:
	
	This has only happened since the recent syscons changes, which were to
	prevent CTRL-ALT and similar combinations from getting stuck down.

	Until a fix is available, switch to a non-X vty and back again.
>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: adam@veda.is
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, 09 Mar 1997 22:47:58 +0900

 >>Environment:
 >
 >	syscons, XFree86 3.2, '@' on RALT+SHIFT+2 in xmodmap.
 >
 >>Description:
 >
 >	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?
 
 >>How-To-Repeat:
 >
 >	Define "keycode 11 = 2 quotedbl 2 at" with xmodmap.
 >	In normal use, press RALT+RSHIFT+2 to type '@'.
 >	Random, probably related to debounce timings.
 >
 >>Fix:
 >	
 >	This has only happened since the recent syscons changes, which were to
 >	prevent CTRL-ALT and similar combinations from getting stuck down.
 
 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.
 
 >	Until a fix is available, switch to a non-X vty and back again.
 
 Kazu

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
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: wosch 
Responsible-Changed-When: Wed Aug 27 15:00:59 PDT 1997 
Responsible-Changed-Why:  
sos is Mr. syscons. 

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: Adam David <adam@veda.is>
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: Mon, 22 Dec 1997 11:08:26 +0900

 Earlier this year, you reported a problem with the keyboard under the
 X environment. At that time, you said you were having the problem with
 3.0-CURRENT and XFree86 3.2.
 
 Do you still see the problem recently?
 
 Kazu
 yokota@freebsd.org
 
 >> >	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

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: Mon, 22 Dec 1997 04:57:25 +0000 (GMT)

 > Earlier this year, you reported a problem with the keyboard under the
 > X environment. At that time, you said you were having the problem with
 > 3.0-CURRENT and XFree86 3.2.
 > 
 > Do you still see the problem recently?
 > 
 > Kazu
 > yokota@freebsd.org
 > 
 > >> >	Define "keycode 11 = 2 quotedbl 2 at" with xmodmap.
 > >> >	In normal use, press RALT+RSHIFT+2 to type '@'.
 > >> >	Random, probably related to debounce timings.
 
 
 I am still seeing it, FreeBSD is updated to recent current, I have not
 changed X since then. Actually it also happens sometimes that other
 shiftkey status gets jammed like this.
 
 Also I still see the problem with Netscape where it is not possible to enter
 deadkey accented characters and RALT+RSHIFT+2 is interpreted as RALT+2, but
 perhaps a more recent Netscape would fix that.
 
 
 Adam David <adam@veda.is>

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: Adam David <adam@veda.is>
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: Mon, 22 Dec 1997 17:32:10 +0900

 >> Earlier this year, you reported a problem with the keyboard under the
 >> X environment. At that time, you said you were having the problem with
 >> 3.0-CURRENT and XFree86 3.2.
 >> 
 >> Do you still see the problem recently?
 >> 
 >> Kazu
 >> yokota@freebsd.org
 >> 
 >> >> >	Define "keycode 11 = 2 quotedbl 2 at" with xmodmap.
 >> >> >	In normal use, press RALT+RSHIFT+2 to type '@'.
 >> >> >	Random, probably related to debounce timings.
 >
 >I am still seeing it, FreeBSD is updated to recent current, I have not
 >changed X since then. Actually it also happens sometimes that other
 >shiftkey status gets jammed like this.
 
 So long as the keyboard is not locked-up, that is, you can hit keys
 and get some responce (even though it may not be the character you
 would expect) and you can switch VTYs by pressing CTL-ALT-Fn, the
 console driver is reading the keyboard correctly. I am beginning to
 think this is a X server problem...
 
 In the X session the X server maintains internal shift states. 
 FreeBSD's console driver just passes key codes to the X server and has
 no idea about the current shift state in the X server.
 
 In your earlier report you stated that if you switch VTYs after the
 shift state is stuck, the state will be restored properly. I guess
 this is because the X server resets its internal key states when
 switching VTYs. (I know the X server resets mouse state during VTY
 switch, so I am assuming similar behavior regarding the keyboard as
 well.)
 
 Have you considered upgrading to XFree86 3.3 or 3.3.1?
 
 >Also I still see the problem with Netscape where it is not possible to enter
 >deadkey accented characters and RALT+RSHIFT+2 is interpreted as RALT+2, but
 >perhaps a more recent Netscape would fix that.
 
 Kazu
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Mar 29 18:12:02 PST 1999 
State-Changed-Why:  
Timed out waiting for followup from newer XFree86 release. 
>Unformatted:
