From owner-freebsd-x11@FreeBSD.ORG Thu Jun 19 11:36:31 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12E96106567C for ; Thu, 19 Jun 2008 11:36:31 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id B7AF88FC15 for ; Thu, 19 Jun 2008 11:36:30 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id BEE5274400B for ; Thu, 19 Jun 2008 14:11:30 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-uyEWnXBhuM for ; Thu, 19 Jun 2008 14:11:30 +0300 (EEST) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [91.198.50.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 7C13F744009 for ; Thu, 19 Jun 2008 14:11:30 +0300 (EEST) Message-ID: <485A3EE1.8070601@icyb.net.ua> Date: Thu, 19 Jun 2008 14:11:29 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.14 (X11/20080611) MIME-Version: 1.0 To: freebsd-x11@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: capslock led after upgrade to xorg-server-1.4.2,1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2008 11:36:31 -0000 Maybe this is related to some other port but I strongly believe that this happened after I upgraded to xorg-server-1.4.2,1. I have very customized xkb configuration where Caps Lock key is used as layout switch key and Pause/Break is used for original Caps Lock functions. I use this configuration for quite a while and everything used to be ok. After the upgrade the keys continue to work as expected. The only issue is that now both Caps Lock and Pause/Break affect state of Caps Lock LED. And this is quite annoying. I want to report this issue here first, maybe someone would have an advice for me what and where to check. However I guess that this is an upstream issue. Here's relevant snippets from my XKB config: partial modifier_keys xkb_symbols "multi_scrl_caps" { ... replace key { type="ONE_LEVEL", [ Caps_Lock ], actions= [ LockMods(modifiers=Lock) ] }; replace key { type="ONE_LEVEL", [ Caps_Lock ], actions= [ LockMods(modifiers=Lock) ] }; ... replace modifier_map Lock { Caps_Lock }; }; ... partial modifier_keys xkb_symbols "caps" { replace key { type = "CTRL+SHIFT", // Base, Ctrl, Shift symbols[Group1] = [ NoSymbol, NoSymbol, NoSymbol ], symbols[Group2] = [ NoSymbol, NoSymbol, NoSymbol ], symbols[Group3] = [ NoSymbol, NoSymbol, NoSymbol ], actions[Group1] = [ NoAction(), LockGroup(group=+1), LockGroup(group=+2) ], actions[Group2] = [ SetGroup(group=+2), LockGroup(group=+1), LockGroup(group=+2) ], actions[Group3] = [ SetGroup(group=+1), LockGroup(group=+1), LockGroup(group=+2) ] }; }; -- Andriy Gapon