Date: Thu, 19 Jun 2008 20:15:35 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: "Paul B. Mahol" <onemda@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: capslock led after upgrade to xorg-server-1.4.2,1 Message-ID: <485A9437.6020305@icyb.net.ua> In-Reply-To: <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com> References: <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <485A69DD.4000308@icyb.net.ua> <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 19/06/2008 19:08 Paul B. Mahol said the following:
> On 6/19/08, Andriy Gapon <avg@icyb.net.ua> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485A9437.6020305>