Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jun 2008 18:08:10 +0200
From:      "Paul B. Mahol" <onemda@gmail.com>
To:        "Andriy Gapon" <avg@icyb.net.ua>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: capslock led after upgrade to xorg-server-1.4.2,1
Message-ID:  <3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc@mail.gmail.com>
In-Reply-To: <485A69DD.4000308@icyb.net.ua>
References:  <485A3EE1.8070601@icyb.net.ua> <3a142e750806190637l35ccda0dt24d9f5595db563d0@mail.gmail.com> <485A69DD.4000308@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

> 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
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750806190908n6c0bb3a6j5d71f871c5fff6fc>