On Tue, 2016-12-13 at 09:44 +0100, Milan Crha wrote:
On Mon, 2016-12-12 at 12:43 -0600, Michael Catanzaro wrote:
That sounds highly plausible. evolution currently shells out to gpg which is pretty fragile, so it's not very surprising that some issue could cause it to hang forever. It needs to be rewritten to use GPGME.
Hi, I looked on GPGME sometime in the beginning of the year and it's missing some features the evolution(-data-server) uses. I do not recaal what exactly, I'm sorry. It's still just a front end for the gpg/ggp2 binary, thus basically the same what the evolution-data-server does.
These things are run in a dedicated thread, thus they do not block the UI, only may result in an infinite wait for a response from the gpg/gpg2. It doesn't result in a timeout though. Being it about gpg/gpg2, I'd reference: https://bugzilla.gnome.org/show_bug.cgi?id=769204
Being it about WebKit2 usage as such (the 3.22.x uses WebKit2, while 3.20.x used WebKit1), I'd reference for example: https://bugzilla.redhat.com/show_bug.cgi?id=1398806#c2
Hope it helps, Milan
The first one GNOME Bugzilla – Bug 769204 says: Status: RESOLVED NOTGNOME
The second one Bug 1398806 - Weird rendering for Evolution on Wayland doesn't seem to apply.
In the past when evolution blocked on gpg messages it was because I didn't have the correct url to the cert for the sig or encryption. could that still be the case here?
I have also noticed that now when I click reply, and then minimize the evolution window, the reply no longer is interactive. This is new behavior with F25 because I could do that with all prior versions of fedora. But I suspect that some interaction with wayland/evolution is the issue.
Regards, Les H