Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 May 2015 15:16:15 +0200
From:      Michael Schuster <michaelsprivate@gmail.com>
To:        Polytropon <freebsd@edvax.de>
Cc:        Avinash Sonawane <rootkea@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Brightness control in FreeBSD 10.1-RELEASE
Message-ID:  <CADqw_g+AAEorRo0uHYB8raSCsw4iyjqnME=5vW8j21OhO7x8_A@mail.gmail.com>
In-Reply-To: <20150521150934.c08a920f.freebsd@edvax.de>
References:  <CAJ9BSW-w6YvA71zu=zV2e_r4Lg78tCPahCc2_6CBkEDdmairFw@mail.gmail.com> <CAJ-VmomybDZX54aP1UWCZvw-H-JUmbbTaocmg4X_kHw7-E1mzg@mail.gmail.com> <CAJ9BSW_Pf5BkL2TJfChy69k9ndCq_4Vku=ExTFFa5RbeWjHbkg@mail.gmail.com> <20150521140123.a18aadc2.freebsd@edvax.de> <CAJ9BSW_uWFMB2=LD7=GMTDm3wGD+Hz5HYuU2YgY89tgpOExVAw@mail.gmail.com> <20150521143734.91ac3a30.freebsd@edvax.de> <CAJ9BSW8RnL9EYc_YjWRAY7t5AxP4BCsWPbGgqPeEvCGw6Ljq8g@mail.gmail.com> <20150521150934.c08a920f.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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 <freebsd@edvax.de> wrote:

> On Thu, 21 May 2015 18:31:57 +0530, Avinash Sonawane wrote:
> > On Thu, May 21, 2015 at 6:07 PM, Polytropon <freebsd@edvax.de> 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/



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CADqw_g+AAEorRo0uHYB8raSCsw4iyjqnME=5vW8j21OhO7x8_A>