When I try to write an email, no matter how I start the process (Clicking the "New"-button, choosing "New" from the "File"-Menu or just click "Reply"), nothing happens for a moment, then a window opens saying "Evolution is not responding" and I can choose between "Force quit" and "Wait". Choosing "Wait", after a few seconds the window just reappears and I have to quit the program. Reproducible: Always Steps to Reproduce: 1.Just try to write an email using one of methods to open the composer. 2. 3. Actual Results: Window opens saying "Evolution is not responding" Force quit/Wait Expected Results: Composer window opens so one can start writing the message to be sent. Complete name of the installed package: evolution-3.50.4-1.fc39.x86_64
Thanks for a bug report. Could you install debuginfo packages: sudo dnf install glib2-debuginfo gtk3-debuginfo evolution-data-server-debuginfo evolution-debugingo --enablerepo=updates-debuginfo and then, when you reproduce the hang (not a crash, right? the app freezes), then get a backtrace of the Evolution in that state, please? You can get the backtrace with a command like this: gdb --batch --ex "t a a bt" --pid=`pidof evolution` &>bt.txt Please check the bt.txt for any private information, like passwords, email addresses, server addresses,... I usually search for "pass" at least (quotes for clarity only), before sharing it anywhere.
Err, I forgot to ask, what is your WebKitGTK version, please? It's: rpm -q webkit2gtk4.1
Created attachment 2018950 [details] debuginfo from evolutiion hang/crash
The version of webkit2gtk is webkit2gtk4.1-2.42.5-1.fc39.x86_64. By the way, I observed that evolution now hangs already when I switch back from the terminal window (to start gdb) to the evolution window. Evolution freezes immediately and the notification window pops up requesting to "Force Quit" or "Wait".
Thanks for the update. The backtrace shows the main thread, the "Thread 1", is idle, which should mean the application is not stuck/frozen. The shell can notice the app unresponsive while the gdb command is running, because gdb stops the app execution until it (gdb) continues the execution or detaches from the process. Simple Alt+Tab between the Evolution window and a terminal window (or other app window) should not cause these freezes for sure. I tried to reproduce it here in a Fedora 39 with the same versions as you use, but no luck, I get no freezes at all.
Ah, my mistake, sorry. I wasn't explicit enough. The freeze happens when I switch to the terminal, start gdb on evolution, and then switch back to evolution again. Switching between evolution and the terminal without invoking gdb... no problem. Sorry, should have mentioned this.
I see. The app can be frozen as long as the gdb is running, which can take some time. The gdb can also waiting for an input (though the --batch mode may avoid it). Could you reproduce the original freeze, when creating a new mail, and while Evolution will be frozen run the gdb command from a terminal, please?
Created attachment 2019095 [details] Backtrace after pressing "New" So, I started evolution and clicked the "New"-button. Immediately afterwards I started gdb. For the output, see the attachment.
Ah, I see, it's waiting for response from gpg. That's bug #2249218, which references upstream https://dev.gnupg.org/T6838 , where you can find a way to correct it. *** This bug has been marked as a duplicate of bug 2249218 ***