Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Dec 2015 00:49:04 +0000
From:      bugzilla-noreply@freebsd.org
To:        x11@FreeBSD.org
Subject:   maintainer-feedback requested: [Bug 205501] x11/xorg fails to handle Logitech Illuminated Keyboard multimedia uhid.
Message-ID:  <bug-205501-7141-lHYgi6cFZf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205501-7141@https.bugs.freebsd.org/bugzilla/>
References:  <bug-205501-7141@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
Mason Loring Bliss <mason@blisses.org> has reassigned Bugzilla Automation
<bugzilla@FreeBSD.org>'s request for maintainer-feedback to x11@FreeBSD.org:
Bug 205501: x11/xorg fails to handle Logitech Illuminated Keyboard multimedia
uhid.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205501



--- Description ---
Created attachment 164476
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164476&action=edit
Xorg.0.log output under Slackware 14.1

My (USB) Logitech Illuminated Keyboard works fine under Linux, but not so fine
under FreeBSD. Under Linux I get keyboard events for multimedia keys -
XF86AudioLowerVolume as an example. I don't get them in FreeBSD. I thought at
first that this was bad handling of the uhid in FreeBSD, but very recently I
noticed that Linux appears to see roughly the same things FreeBSD did.

To clarify this, my initial workaround in FreeBSD was to hack up a version of
usbhidaction that pretended "range" values from uhids didn't exist. This done,
I was able to get discrete values for media keys that I could interpret and act
on appropriately. Now, looking at the same keyboard under Linux, I see that the
uhid that attaches alongside the keyboard is seen as delivering ranges there
too, and yet, something in there is delivering key events when the uhid's keys
are hit.

I'm not sure where to file this, so I'm doing it under x11/xorg for now.

Attachment is the relevant excerpt from my Xorg.0.log under Slackware.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205501-7141-lHYgi6cFZf>