Date: Sun, 9 Mar 1997 05:50:01 -0800 (PST) From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-bugs Subject: Re: i386/2924: syscons X keyboard gets stuck in capsmode Message-ID: <199703091350.FAA22473@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/2924; it has been noted by GNATS. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703091350.FAA22473>