Hello! Claws version: 4.0 OS: ArchLinux DE: i3wm I've discovered a bug that I can reproduce with 100% probability with the setup above. The following steps are required to reproduce it: 1) In the message list, select an encrypted message by left clicking on it. 2) The gnupg prompt will pop up asking for the key master passphrase to decrypt the message. 3) There is a slight time delay between steps 1 and 2. Within this period of time, before the prompt from step 2 popped up, right click on the message selected in step 1 to invoke the context menu for this message. The following happens: The prompt from step 2 pops up, but it doesn't get the input. Now all keyboard and mouse button events are blocked, and the only thing you can do is to move the mouse cursor across the screen. You cannot type, click, switch TTY. Hard reboot is the only option to fix this.
That "slight delay" is basically non-existent here and there's no way to manage a right click before the gnupg-agent dialogue appears. The most I've achieved is for the context menu to show after the gnupg-agent dialogue has been closed.
Well, the described behavior is observed by me in a qemu virtual machine running on a pretty old, not so fast hardware. This might be a reason why I experience this "slight delay". I first encountered the problem when I accidentally clicked on a message with both left and right mouse buttons that led to the entire machine was deadlocked. It happens when the gnupg prompt pop up on the screen after the context menu has been appeared. This report is mostly just for the info. If you consider it not to be an issue, feel free to close it.
Please, ignore this report. I managed to reproduce the issue with gnupg prompt blocks user input outside of ClawsMail. It seems the problem is rather related to i3wm then to ClawsMail. I apologize for wasting your time on the false report.