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

i3lock: possibly lets keypresses slip through due to re-grab of the keyboard #545

Closed
i3bot opened this issue Oct 24, 2011 · 2 comments
Closed

i3lock: possibly lets keypresses slip through due to re-grab of the keyboard #545

i3bot opened this issue Oct 24, 2011 · 2 comments
Assignees
@stapelberg
Labels
4.0

Comments

@i3bot
Copy link

i3bot commented Oct 24, 2011

[Originally reported by anonymous]
(On MappingNotify, we re-grab the keyboard. Since that is not an entirely atomic operation, in some situations keypresses might slip through.

See if we can reproduce that by hammering MappingNotifies and/or loading the machine. Try GrabServer to make this atomic?
@stapelberg
Copy link
Member

The theory was right, I can reproduce it with:

  1. start 4 instances of burnP6 from the cpuburn package
  2. Run this: i=0; while [ $i -lt 100 ]; do setxkbmap us; echo $i; i=$((i+1)); sleep 0.1; done
  3. Start i3lock, enter stuff, notice it slipping through to the last focused terminal

@stapelberg
Copy link
Member

This is fixed in commit a803ba9

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stapelberg stapelberg

Labels
4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stapelberg @i3bot