-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libinput and waynergy #56
Comments
This is the output from initial startup
however nothing can be seen after this output from that point forward. |
running latest wlroots-git, sway-git, and waynergy-git from arch aur |
It will indeed bypass libinput, which is just one of several backends on the wlroots side of things |
Thanks! |
If it's particularly useful, for debugging purposes you can use the uinput waynergy backend with sway as well. This will go through libinput, like any hardware device. |
Technically speaking, how does Waynergy control keyboard/mouse input with wlroots compositors like sway? This issue has existed for ages with no resolution, but everyone reporting it has not found any information from debugging libinput. As I experience this same problem using Waynergy (which is not using libinput), it may reveal that the bug is in fact in wlroots (or sway) |
For the mouse input that seems to be the issue here, it uses this Wayland protocol to do so. For debugging purposes you can export In any case it is almost certainly a sway/wlroots bug; to narrow it down one might consider trying to reproduce using other wlroots compositors. |
Does waynegy's method of communicating with wayland bypass libinput?
I've noticed if I use
libinput debug-events
, keyboard and mouse clicks are not shown.I am trying to debug a frequent issue with swaywm where mouse clicks no longer register.
The text was updated successfully, but these errors were encountered: