talonvoice / talon

Issue Tracker for the main Talon app
85 stars 0 forks source link

Control key fails to trigger after system is woken up (Linux, i3wm) #227

Open aceslowman opened 4 years ago

aceslowman commented 4 years ago

This issue is new for me while using Talon linux beta (1196), after switching from my window manager to i3. After the machine is been woken up from systemctl suspend the control is no longer triggered. For example, if a command for (ctrl-s) is triggered, the result is the printed character 's'. Problem is always resolved with a reboot.

System info: 5.3.0-53-generic talonvoice/beta#47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

aceslowman commented 4 years ago

Last night I updated Talon to 1332 and was able to confirm that the control key works after systemctl suspend. Today, after a long period of inactivity (no suspend), the issue continues.

lunixbochs commented 4 years ago

I'm honestly not sure on this one

lunixbochs commented 4 years ago

See if you can repro on 1424

lunixbochs commented 3 years ago

I think this is fixed in 0.1.5-393, please let me know if it's not and we can look into what to do next

lunixbochs commented 3 years ago

Reopening, fidget just encountered this issue.

xev showed the ctrl key press was happening but not affecting device flags. Also typically a MappingNotify would happen, but was not present with Talon.

pressing ctrl-c with Talon

KeyPress event, serial 35, synthetic NO, window 0x9000001,
    root 0x5eb, subw 0x0, time 668215468, (167,814), root:(1890,860),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
KeyPress event, serial 35, synthetic NO, window 0x9000001,
    root 0x5eb, subw 0x0, time 668215469, (167,814), root:(1890,860),
    state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (63) "c"
    XmbLookupString gives 1 bytes: (63) "c"
    XFilterEvent returns: False
KeyRelease event, serial 35, synthetic NO, window 0x9000001,
    root 0x5eb, subw 0x0, time 668215472, (167,814), root:(1890,860),
    state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (63) "c"
    XFilterEvent returns: False
KeyRelease event, serial 35, synthetic NO, window 0x9000001,
    root 0x5eb, subw 0x0, time 668215474, (167,814), root:(1890,860),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

pressing ctrl-c on the keyboard

MappingNotify event, serial 36, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248
KeyPress event, serial 36, synthetic NO, window 0x8e00001,
    root 0x5eb, subw 0x0, time 668468271, (219,574), root:(1942,620),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
KeyPress event, serial 37, synthetic NO, window 0x8e00001,
    root 0x5eb, subw 0x0, time 668468415, (219,574), root:(1942,620),
    state 0x4, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (03) ""
    XmbLookupString gives 1 bytes: (03) ""
    XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x8e00001,
    root 0x5eb, subw 0x0, time 668468551, (219,574), root:(1942,620),
    state 0x4, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (03) ""
    XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x8e00001,
    root 0x5eb, subw 0x0, time 668468879, (219,574), root:(1942,620),
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
lunixbochs commented 3 years ago

xdotool exhibits the same behavior, maybe this isn't a Talon bug?

lunixbochs commented 2 years ago

I won't be in a position to reproduce this issue unless I run Linux daily - so until I try that, this issue is stalled unless a user wants to figure out why it's happening.