Bug 1005701

Summary: [abrt] evolution-3.9.91-2.fc20: g_mutex_get_impl: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Björn 'besser82' Esser <besser82>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ekanter, im_asmodeus, im.grocc, lucilanga, mbarnes, mcrcctm, mcrha, oliveriandrea, vitaliyparitskiy, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3909bebf9737a8ce1fd0a45512a4e8934937caf8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-10 07:21:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Björn 'besser82' Esser 2013-09-09 08:44:15 UTC 
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:
evolution-3.9.91-2.fc20

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        evolution
crash_function: g_mutex_get_impl
executable:     /usr/bin/evolution
kernel:         3.11.0-300.fc20.x86_64
runlevel:       unknown
uid:            1000

Truncated backtrace:
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
Comment 1 Björn 'besser82' Esser 2013-09-09 08:44:23 UTC 
Created attachment 795531 [details]
File: backtrace
Comment 2 Björn 'besser82' Esser 2013-09-09 08:44:26 UTC 
Created attachment 795532 [details]
File: cgroup
Comment 3 Björn 'besser82' Esser 2013-09-09 08:44:30 UTC 
Created attachment 795533 [details]
File: core_backtrace
Comment 4 Björn 'besser82' Esser 2013-09-09 08:44:33 UTC 
Created attachment 795534 [details]
File: dso_list
Comment 5 Björn 'besser82' Esser 2013-09-09 08:44:37 UTC 
Created attachment 795535 [details]
File: environ
Comment 6 Björn 'besser82' Esser 2013-09-09 08:44:40 UTC 
Created attachment 795536 [details]
File: exploitable
Comment 7 Björn 'besser82' Esser 2013-09-09 08:44:43 UTC 
Created attachment 795537 [details]
File: limits
Comment 8 Björn 'besser82' Esser 2013-09-09 08:44:47 UTC 
Created attachment 795538 [details]
File: maps
Comment 9 Björn 'besser82' Esser 2013-09-09 08:44:51 UTC 
Created attachment 795539 [details]
File: open_fds
Comment 10 Björn 'besser82' Esser 2013-09-09 08:44:55 UTC 
Created attachment 795540 [details]
File: proc_pid_status
Comment 11 Björn 'besser82' Esser 2013-09-09 08:45:01 UTC 
Created attachment 795541 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-09-10 07:21:20 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=707830
Comment 13 Eugene Kanter 2014-01-24 18:42:39 UTC 
There appears to be a fix in upstream. Are there any plans for a backport?
Comment 14 Milan Crha 2014-01-27 10:05:58 UTC 
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).