| Summary: | UI frozen when exiting external editor | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | Nicola Fontana <ntd> | ||||||
| Component: | UI | Assignee: | users | ||||||
| Status: | NEW --- | ||||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 3.14.1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Attachments: |
|
||||||||
Created attachment 1716 [details]
Triggering a close window solves the problem
|
Created attachment 1715 [details] Screenshot of frozen claws-mail Sometime the UI freezes when exiting the external editor (gvim in my case). The editor is spawned in foreground. Actually I'm using the default embedded gvim command but it was happening also with the non-embedded one (gvim -f %s), so I am pretty sure it is not GtkSocket related: [nicola@iota .claws-mail]$ grep ext_editor_command clawsrc ext_editor_command=gvim -f --socketid %w %s I had hard time trying to figure out how to replicate the problem and I still do not fully understand the problem... it seems something related to focus. Anyway I spawn the external text editor, switch desktop and select something in another program, return to the desktop where claws-mail resides and exit the text editor (:wq). After that I get what is shown in the first screenshot: the window is frozen and do not repaint itself anymore. My current ugly workaround is triggering a close window request via keyboard. After a couple of seconds I get what shown in the second screenshot: a confirmation dialog appears and the compose window is properly populated with what I written in the external editor.