Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error Unexpected X11 event: 65 when triggering keynav #51

Open
sim590 opened this issue Apr 23, 2020 · 7 comments · May be fixed by #63
Open

Error Unexpected X11 event: 65 when triggering keynav #51

sim590 opened this issue Apr 23, 2020 · 7 comments · May be fixed by #63

Comments

@sim590
Copy link

sim590 commented Apr 23, 2020

At some point, which I can't describe with more details, keynav will cause the keyboard to freeze with the error Unexpected X11 event: 65. I have to kill keynav (by jumping in an old-school TTY terminal) in order to get the control of the keyboard back. Once it happens a first time, there's nothing to do. Every time keynav will be restarted and triggered by the appropriate keystroke, the same thing will happen. There nothing to do other than restarting X in order to "fix it" for a while. I don't know how to reproduce for now.
@sitepodmatt
Copy link

Seeing this in i3wm too

@eyalev
Copy link

eyalev commented Nov 23, 2020

Happens to me when the keyboard is on a Hebrew layout instead of English

@sitepodmatt
Copy link

sitepodmatt commented Nov 23, 2020 •
edited
Loading

Im on en_US keyboard and it happens to me at launch Unexpected X11 event: 65` after the targetter is overlaid, hjlk are useless at point of launch. It may have something to do with switching to regolith linux in last few days so my compositor has changed picom, unsure.

@exAClior
Copy link

Using manjaro Linux with xmonad + picom, seeing this too

@sitepodmatt
Copy link

Killing picom it seems to work. So I think it is a compositor problem.

@PaddiM8
Copy link

PaddiM8 commented Dec 23, 2020

Yeah picom seems to be the problem for me as well. Does anyone know how to get around this?

@ryanthomas-org
Copy link

Is this the same issue as #42 ? Commenting out XUnmapWindow(dpy, zone); in keynav.c resolved this for me. I never had to kill keynav from TTY though. I'd lose control of keyboard but in reality the escape key sufficed to close the program; the grid was simply not displaying. Commenting out the line in question yielded the same result for me as killing picom did. Thanks!

@aflyingpumpkin aflyingpumpkin linked a pull request Jan 28, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added config option 'picomfix' to fix disappearing in picom. aflyingpumpkin/keynav
6 participants
@eyalev @sitepodmatt @sim590 @exAClior @PaddiM8 @ryanthomas-org