When typing a message, thunderbird sometimes starts to interpret written characters as commands. E.g. when writing 'know', it writes 'k' and then switches to the command mode and interprets 'n' as 'read a new message'. Of course, there are much more dangerous commands like 'a' etc, therefore 'critical'. When I used thunderbird-17.0.9, it never happened. Reproducible: Sometimes Steps to Reproduce: 1. Try to write a new message multiple times (it happens rarely, maybe when typing 1 message from 10). Actual Results: Sometimes thunderbird starts to interpret characters as commands, e.g. 'n' for reading a new message. Expected Results: Nothing special, just typing my message.
Did you consider the possibility of the source of the problem being a key occasionally getting stuck ?
I don't think so, it didn't appear to get stuck. Anyway, even if it did, it'd be weird behavior to enter the command mode. In previous versions (maybe v24.2, I'm not sure) it sometimes even forbade me to edit a new message and it persisted until I restarted Thunderbird. Fortunately forbidding is not an issue of v24.6. P.S. Thanks for your very quick answer.
Any progress? It's not a way to write an e-mail letter-by-letter, checking whether it hasn't switched into the command mode. And neither writing an e-mail in another editor (like vim) and pasting it into TB.
At last I've found the source of the problem: _unclutter_. If anyone needs to use unclutter, add -noevents to its parameters and the problem disappears. If anyone wants to experience the described problem you can do it this way (I found this to work with TB 24.2 & 24.8 every time I tried): 1) $ unclutter & 2) $ thunderbird 3) click on any e-mail; 4) move the mouse cursor away from the area where the window for a new message will appear but still over the window of TB; 5) Ctrl-N by the time the mouse cursor disappears (it must be visible until the window for a new message is fully created); 6) wait for the mouse cursor to disappear; 7) type 'm' and you will see your selected message to be marked as unread, although the window for a new message is active (the reason is that unclutter (v8-r2) sends EnterNotify to the window under the cursor). You can try the same with "$ unclutter -noevents &" and you will see the problem disappear ("$ pkill unclutter" in advance). Thank you for your precious time and sorry for my mistake; but I hope this page can help others.
