From owner-freebsd-questions@FreeBSD.ORG Thu May 21 13:09:37 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4880A9B2 for ; Thu, 21 May 2015 13:09:37 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06B1A1A62 for ; Thu, 21 May 2015 13:09:36 +0000 (UTC) Received: from r56.edvax.de (port-92-195-181-19.dynamic.qsc.de [92.195.181.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id F1C012785F; Thu, 21 May 2015 15:09:34 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t4LD9Y7N003391; Thu, 21 May 2015 15:09:34 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 21 May 2015 15:09:34 +0200 From: Polytropon To: Avinash Sonawane Cc: FreeBSD Questions Subject: Re: Brightness control in FreeBSD 10.1-RELEASE Message-Id: <20150521150934.c08a920f.freebsd@edvax.de> In-Reply-To: References: <20150521140123.a18aadc2.freebsd@edvax.de> <20150521143734.91ac3a30.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 13:09:37 -0000 On Thu, 21 May 2015 18:31:57 +0530, Avinash Sonawane wrote: > On Thu, May 21, 2015 at 6:07 PM, Polytropon wrote: > > > This is only for one of the keys (code 133), what about the > > other one? > > For other one I got same never ending loop. > I guess these are the relevant specifics: > > KeyRelease event, serial 37, synthetic NO, window 0x1e00001, > root 0x2b9, subw 0x0, time 3656195, (96,113), root:(690,436), > state 0x10, keycode 134 (keysym 0xffae, KP_Decimal), same_screen YES, > XLookupString gives 1 bytes: (2e) "." > XFilterEvent returns: False > > KeyPress event, serial 37, synthetic NO, window 0x1e00001, > root 0x2b9, subw 0x0, time 3656195, (96,113), root:(690,436), > state 0x10, keycode 134 (keysym 0xffae, KP_Decimal), same_screen YES, > XLookupString gives 1 bytes: (2e) "." > XmbLookupString gives 1 bytes: (2e) "." > XFilterEvent returns: False Yes. Somehow _this_ key combination (code 134) is assigned to the keypad decimal point (numeric keypad decimal separator, usually code 93), which is wrong - but matches your observation that dots will appear in input fields. I have no idea where this code is introduced. Maybe some crazy auto-detect "magic" usually found in big desktop environments? > > If you find a way to modify screen brightness using a command, > > you can use xmodmap and xbindkeys to connect that command to > > a keypress of that key. > > I guess that'll work. I am looking at `man acpi_video` which talks > about sysctling brightness variables. When you have commands that work, you can start "programming the keys" to act as intended, using xmodmap. It's still strange why code 133 and 134 are being treated that way. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...