Red Hat Bugzilla – Bug 1005701
[abrt] evolution-3.9.91-2.fc20: g_mutex_get_impl: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2014-08-27 06:13:16 EDT
Description of problem:
I just changed some settings of an account and apllied them. When clicking on "apply", evolution crashed with this.
Version-Release number of selected component:
Thread no. 1 (10 frames)
#0 g_mutex_get_impl at gthread-posix.c:124
#1 g_mutex_lock at gthread-posix.c:213
#2 imapx_start_idle at camel-imapx-server.c:3343
#3 imapx_command_start_next at camel-imapx-server.c:1044
#4 imapx_completion at camel-imapx-server.c:2780
#5 imapx_step at camel-imapx-server.c:2815
#6 imapx_parse_contents at camel-imapx-server.c:6764
#7 imapx_parser_thread at camel-imapx-server.c:6830
#8 g_thread_proxy at gthread.c:798
#10 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Created attachment 795531 [details]
Created attachment 795532 [details]
Created attachment 795533 [details]
Created attachment 795534 [details]
Created attachment 795535 [details]
Created attachment 795536 [details]
Created attachment 795537 [details]
Created attachment 795538 [details]
Created attachment 795539 [details]
Created attachment 795540 [details]
Created attachment 795541 [details]
Thanks for a bug report. I moved this upstream as . Please see  for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.
There appears to be a fix in upstream. Are there any plans for a backport?
Right, it depends whether the change is applicable to 3.10.3 at all, but if the upstream developer will provide a fix for 3.10.3, then it might be part of 3.10.4 release, which will be added to Fedora once it's out (in other words, I'd wait for the upstream with this, because the change itself doesn't look trivial).