From owner-freebsd-x11@FreeBSD.ORG Thu Jun 19 18:05: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 28A681065680 for ; Thu, 19 Jun 2008 18:05:31 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id C63BD8FC0C for ; Thu, 19 Jun 2008 18:05:30 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1K9NjY-000MoS-Hq; Thu, 19 Jun 2008 20:15:40 +0300 Message-ID: <485A9437.6020305@icyb.net.ua> Date: Thu, 19 Jun 2008 20:15:35 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.14 (X11/20080517) MIME-Version: 1.0 To: "Paul B. Mahol" References: <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <485A69DD.4000308@icyb.net.ua> <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> In-Reply-To: <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org Subject: Re: 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 18:05:31 -0000 on 19/06/2008 19:08 Paul B. Mahol said the following: > On 6/19/08, Andriy Gapon wrote: >> on 19/06/2008 16:37 Paul B. Mahol said the following: >>> It is upstream issue/regression. I liked how it was before ... but >>> Xorg devs have different opinion. >> Could you please expand a little bit on this? particular commit or >> discussion or something? >> > > xset led {1-32} doesnt work any more as it was before (only Scroll > Lock LED can be turned on/off). > > I guess it was caused by new version of xf86-input drivers, I never > found issue so imortant to fix it myself. I don't think that this is related to my issue. In fact, I think that what you described is controlled by xkeyboard-config settings. In /usr/local/share/X11/xkb/compat/led* allowExplicit is set only for Scroll Lock, Num Lock and Caps Lock have !allowExplicit. That means that X applications can not directly change them, which is exactly what you describe. This is still configurable, but not in a convenient way though. >> BTW, what's strange too is that if I use xkbvleds then it reflects Caps >> Lock LED changes caused by "new"/remapped Caps Lock button but it >> doesn't respond to the "old"/normal Caps Lock button. But physical LED >> responds to both. >> >> -- >> Andriy Gapon >> -- Andriy Gapon