Hi, i meet this issue recent days since i reinstall a new refresh arch linux (GNOME3 + Wayland)
At the beginning, i suspect if this is a issue caused by my keyboard, system, or the
way start xkeysnail. (.config/autostart/xkeysnail.desktop).
But, finally, i found this issue caused by xkeysnail, because when i kill xkeysnail,
the no respond key is start to works again.
In fact, i am not sure if this issue always happen, because no respond key is random,
if that key is a rarely used key, i could not find out anyway.
And, occasionally, even all input key is no respond, (But Ctrl+C, or Ctrl+Alt+F3 still working),
after i open a login session, and kill xkeysnail, start to works again, i guess this case caused
by some prefix key(e.g. CTRL) is keeping pressed status.
If you need more debug detail, please tell me how to. thank you.
Hi, i meet this issue recent days since i reinstall a new refresh arch linux (GNOME3 + Wayland)
At the beginning, i suspect if this is a issue caused by my keyboard, system, or the way start xkeysnail. (.config/autostart/xkeysnail.desktop).
But, finally, i found this issue caused by xkeysnail, because when i kill xkeysnail, the no respond key is start to works again.
In fact, i am not sure if this issue always happen, because no respond key is random, if that key is a rarely used key, i could not find out anyway.
And, occasionally, even all input key is no respond, (But Ctrl+C, or Ctrl+Alt+F3 still working), after i open a login session, and kill xkeysnail, start to works again, i guess this case caused by some prefix key(e.g. CTRL) is keeping pressed status.
If you need more debug detail, please tell me how to. thank you.