From owner-freebsd-questions@FreeBSD.ORG Thu May 21 13:16:36 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 E7D6AEE8 for ; Thu, 21 May 2015 13:16:36 +0000 (UTC) Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B44AD1BA6 for ; Thu, 21 May 2015 13:16:36 +0000 (UTC) Received: by pdfh10 with SMTP id h10so107943495pdf.3 for ; Thu, 21 May 2015 06:16:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RdK87jiI5T4yDEepslzkZpUid9ZMVC1+d40acoXISmw=; b=KlRw+0ZnucY/v3TQomPIDkJqxkhmi0f2NpruboNynG99pMKEtIuKbLAFwvmSLZSO5m KeVCdOfEbtlx/yjrMydfMfjgk9ofOd9w/gE3vj9P+Q+3N/+tkSmSx2Z+7wCLp5p+UxWr hKVCOjeHpmqYG2XuLGHY6ev4mMz99m6XHRaKZtYaAQBV/euZ+Q2jgoCo9Yi37PV9VJrx iEB3V6dykVM4WHa5W2A0pHkIt1RwR1hthaohKElvAPMk/8nRO2D23zVnCAW449EudEkJ kKpyOSXnjHMsDMpvjCGyW5xz56pSP163qkWJ6Zmu/X61ZJX9WV4hsFOBscMpwhZl4PX0 wszA== X-Received: by 10.70.49.229 with SMTP id x5mr5381454pdn.81.1432214195877; Thu, 21 May 2015 06:16:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.68.67 with HTTP; Thu, 21 May 2015 06:16:15 -0700 (PDT) In-Reply-To: <20150521150934.c08a920f.freebsd@edvax.de> References: <20150521140123.a18aadc2.freebsd@edvax.de> <20150521143734.91ac3a30.freebsd@edvax.de> <20150521150934.c08a920f.freebsd@edvax.de> From: Michael Schuster Date: Thu, 21 May 2015 15:16:15 +0200 Message-ID: Subject: Re: Brightness control in FreeBSD 10.1-RELEASE To: Polytropon Cc: Avinash Sonawane , FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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:16:37 -0000 I find that window managers (I use enlightenment) often have options to set these key bindings ... maybe yours is interfering. Have you checked something like that? HTH Michael On Thu, May 21, 2015 at 3:09 PM, Polytropon wrote: > 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, ... > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- Michael Schuster http://recursiveramblings.wordpress.com/