search

khampf / g13

libusb driver for the g13
23 stars 15 forks source link

Issues with libinput 1.15.902 #6

Closed banduccm closed 4 years ago

banduccm commented 4 years ago

I'm using g13d on Fedora 32. I was running a version I built myself from back in March, and today it stopped working. I was unable to get keypress events in Gnome, but using 'showkey' I could see that the proper key events were being sent. When I switched to a VT, g13d worked as expected - I saw the correct output on the terminal. I went back through my update history and saw that libinput updated to libinput-1.15.902-1.fc32.x86_64. I rolled back the update (to libinput 1.15.4) and g13d started working again.

I see the same behavior with your latest release binary (1.0.4).

Curiously, I'm getting a core dump when I try to build your latest g13d master branch against libinput-devel-1.15.902-1.fc32.x86_64. I'm going to try to dig into that a bit more and see if I can learn anything, but I'm new to Linux development, so it may take me a bit.

Please let me know if there's anything I can do to be helpful here or if there are more details I can provide.

Thank you!

System: Fedora 32, Kernel 5.7.11-200.fc32.x86_64

banduccm commented 4 years ago

I did some debugging and I can confirm that the crash I'm seeing has nothing to do with the libinput issue.

I rebuilt a working version locally with libinput 1.15.902 and I still have the same lack of input problems. Rolling back to 1.15.4 makes it work again. I'm guessing this is a libinput problem, but I'll have to learn more about how g13d interfaces with libinput to see if it's something that needs to change here, or a bug that should be reported upstream.

khampf commented 4 years ago

As Arch Linux is currently using 1.15.6 I could try recompiling against that library version but I use my g13d daily and I seem not to experience the same issues. But do follow up if you have the time, it could potentially stop a bug from coming at me in the future :-)

banduccm commented 4 years ago

Fedora updated to libinput 1.16 today (libinput-1.16.0-1.fc32.x86_64), and g13d appears to be working perfectly. I'll let you know if I run into any other issues, but for now, things look good!