This button sends a release N, press N+1 on each press, cycling through the
three event codes supported. This causes a stuck button since the current mode
is never released.
Long-term this better served by a set of switches that toggle accordingly, for
now disable the button codes.
https://bugs.f
Hi,
On 01/29/2016 01:48 AM, Peter Hutterer wrote:
This button sends a release N, press N+1 on each press, cycling through the
three event codes supported. This causes a stuck button since the current mode
is never released.
Long-term this better served by a set of switches that toggle according
On Wed, Feb 03, 2016 at 06:47:01PM +, Joel Duncan wrote:
>
> Hi guys,
>
> Not being a libinput dev I was looking for advice on using this patch.
> I noticed that a lot of the RAT config was in /test. After compiling the
> driver
> and installing it the problem still persists.
>
> I'm assum
On Wed, Feb 03, 2016 at 10:43:03PM +, Joel Duncan wrote:
> Thanks for clearing that up, Can confirm the patch works.
>
> udev rules were put in /usr/local/lib/udev by make command, moved to
> /usr/lib/udev then devadm hwdb --update.
>
for next time:
./configure --prefix=/usr --libdir=/usr
Thanks for clearing that up, Can confirm the patch works.
udev rules were put in /usr/local/lib/udev by make command, moved to
/usr/lib/udev then devadm hwdb --update.
Looking forward to seeing this in upstream Fedora one day.
Thanks,
Joel
On Wed, Feb 3, 2016 at 9:30 PM, Peter Hutterer
wrote
Hi guys,
Not being a libinput dev I was looking for advice on using this patch.
I noticed that a lot of the RAT config was in /test. After compiling the
driver
and installing it the problem still persists.
I'm assuming it's due to needing a flag when compiling to include /test
components?
Any