Alphanum keys stop working after a short while

Thanks for filing an issue! Please answer the questions below so I can help you.

• iTerm2 version: 3.1.beta.5
• OS version: OS X 10.11.6
• Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) com.googlecode.iterm2.plist
• Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog debuglog.txt
• Are you reporting a performance issue or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
• Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs

Detailed steps to reproduce the problem:

1. Start a session
2. Start typing some things into the session for a while

What happened: The alphanumeric keys become unresponsive. Ctrl+ commands and arrow keys still work, for instance, but I can't type anything.

What should have happened: Typing alphanumeric characters should work.

Something got Cocoa's text input in a funny mode. We pass the keystroke to the system to handle and it never gives it back to us to insert. Do you have a $HOME/Library/KeyBindings/DefaultKeyBinding.dict file? If so, please share a copy with me.

Do you have multiple keyboard types defined (e.g., English and some other language?) If so, is English still selected after this occurs?

I think it's a long shot, but does turning off Prefs > Advanced > Improved support for input method editors like AquaSKK prevent the issue from occurring?

I do not have that keybindings file.

I don't have multiple keyboard types defined.

AquaSSK support is already off.

After rebooting, I haven't been able to reproduce, however.

This is happening to me again with newer versions of iTerm (Build 3.1.beta.9).

This time, AquaSKK was on, so I turned it off.

Waiting to see if that fixes it.

So far, turning off AquaSKK seems to have done the trick

It looks like holding down a key to make it repeat is what triggers the problem. Does that consistently do it for you when AquaSKK support is on?

changed milestone to %Review for next version

Yes! That seems to do it for me.

I'm not sure what the cause is. I'll wait to see if anyone else reports a similar issue, since the new text handling path is much nicer than the old one.