You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Unlike all the other media keys I have set up in my configuration file, the XF86TouchpadToggle key presses are being ignored for what seems like an arbitrary number of presses. These can go from just a couple of key presses until the desired action is executed to well over 10 key presses. The problem is also present when binding the key by keycode.
I know that the physical key is working correctly because wev is consistently picking it up, although it seems to have quite a bit of extra output for it compared to most of my other media keys:
Something that might (or might not) be of interest is that while trying to generate Sway's logfile for this issue each press of XF86TouchpadToggle generated a ^@ on the TTY. While attempting to turn off and then back on the touchpad (which took a total amount of 14 XF86TouchpadToggle key presses instead of the expected 2) this is how my terminal looked:
Sway Version:
sway version 1.10
Debug Log:
Configuration File:
Unlike all the other media keys I have set up in my configuration file, the
XF86TouchpadToggle
key presses are being ignored for what seems like an arbitrary number of presses. These can go from just a couple of key presses until the desired action is executed to well over 10 key presses. The problem is also present when binding the key by keycode.I know that the physical key is working correctly because
wev
is consistently picking it up, although it seems to have quite a bit of extra output for it compared to most of my other media keys:Something that might (or might not) be of interest is that while trying to generate Sway's logfile for this issue each press of
XF86TouchpadToggle
generated a^@
on the TTY. While attempting to turn off and then back on the touchpad (which took a total amount of 14XF86TouchpadToggle
key presses instead of the expected 2) this is how my terminal looked:The text was updated successfully, but these errors were encountered: