Comment 26 for bug 66104

I can reproduce the error by opening a bash terminal and hitting ctrl+shift+t many times without pausing. When I do this, not _all_ keyboard input is blocked:
* ctrl-shift-t and ctrl-shift-w work (open and close tabs)
* I can copy text with ctrl-shift-c
* alt-F4 works, to close the window

Another weird behaviour:
What I do, variant A:
* I open one terminal
* I type some special character (ä, ü, à, etc.)
* I open a new terminal with ctrl-shift-n (sometimes it also happens when i switch to an existing terminal window)

What I do, variant B:
* I open one terminal (this works also with thunderbird)
* I open a new terminal with ctrl-shift-n
* Before the new terminal is ready, i type anything.

What i get:
* Both windows are basically keyboard blocked.
* But not really, I give some examples:
- close all terminals (works the same with thunderbird)
- open new terminal (I call it window1)
- ctrl-shift-n and without delay n (or any other letter). window2 appears.
- input (window2): hello. no reaction.
- alt-tab (works fine, focus changes to window1.)
- input: gugus (and here, at the first key stroke, the n appears in window2, along with the first g in window1!)
- alt-tab (focus on window2 again, nothing else happens.)
- alt-tab (focus on window1, nothing else)
- input: x (xugus appears, making sxugus).

It's not always exactly the same, but there seems to be something wrong with the assigning of input to a certain window if one does not wait for the window to completely build before one types. With Thunderbird, it's much worse because the same thing happens and there, the windows take more time to load.

I don't know it that's the same bug as the one above, but it seems to me.

Thanks to anyone who tries to find a solution to this!
Christoph