From owner-freebsd-x11@FreeBSD.ORG Thu Jun 19 18:06:16 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 03652106564A for ; Thu, 19 Jun 2008 18:06:16 +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 A50698FC1B for ; Thu, 19 Jun 2008 18:06:15 +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 1K9OWU-000NuW-Td for freebsd-x11@freebsd.org; Thu, 19 Jun 2008 21:06:14 +0300 Message-ID: <485AA016.9050203@icyb.net.ua> Date: Thu, 19 Jun 2008 21:06:14 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.14 (X11/20080517) MIME-Version: 1.0 To: freebsd-x11@freebsd.org References: <485A3EE1.8070601@icyb.net.ua> In-Reply-To: <485A3EE1.8070601@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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:06:16 -0000 on 19/06/2008 14:11 Andriy Gapon said the following: > 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. And by the way, commit message for update of x11-servers/xorg-server to 1.4.2 is quite misleading. It says that it is just a security update. But in fact 1.4.1=>1.4.2 change is a security update and our port used to have version 1.4[.0], and there were some larger functionality changes between 1.4=>1.4.0.90=>1.4.1 which the port didn't get before. -- Andriy Gapon