Bug 1098631

Summary: [abrt] evolution: __pthread_mutex_lock(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Pavel Mlčoch <pavkamlc>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, fabrice, lucilanga, mbarnes, mcrha, pavkamlc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cfce9fe9d72eb453d46296cc6c38f460d50108e2
Whiteboard: abrt_hash:ab0310bba15b66458a4fbac5205fbdd0da80604a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:39:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 Pavel Mlčoch 2014-05-16 18:16:56 UTC 
Version-Release number of selected component:
evolution-3.10.4-2.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        evolution
crash_function: __pthread_mutex_lock
executable:     /usr/bin/evolution
kernel:         3.14.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66
 #1 g_mutex_lock at gthread-posix.c:213
 #2 g_main_loop_quit at gmain.c:3932
 #3 source_registry_authenticate_respond_cb at e-source-registry.c:1777
 #7 g_main_context_iteration at gmain.c:3774
 #8 e_source_registry_authenticate_sync at e-source-registry.c:2119
 #9 mail_session_authenticate_sync at e-mail-session.c:1608
 #10 camel_session_authenticate_sync at camel-session.c:1829
 #11 ews_connect_sync at camel-ews-store.c:658
 #12 service_connect_thread at camel-service.c:773
Comment 1 Pavel Mlčoch 2014-05-16 18:17:03 UTC 
Created attachment 896490 [details]
File: backtrace
Comment 2 Pavel Mlčoch 2014-05-16 18:17:05 UTC 
Created attachment 896491 [details]
File: cgroup
Comment 3 Pavel Mlčoch 2014-05-16 18:17:08 UTC 
Created attachment 896492 [details]
File: core_backtrace
Comment 4 Pavel Mlčoch 2014-05-16 18:17:11 UTC 
Created attachment 896493 [details]
File: dso_list
Comment 5 Pavel Mlčoch 2014-05-16 18:17:13 UTC 
Created attachment 896494 [details]
File: environ
Comment 6 Pavel Mlčoch 2014-05-16 18:17:15 UTC 
Created attachment 896495 [details]
File: exploitable
Comment 7 Pavel Mlčoch 2014-05-16 18:17:17 UTC 
Created attachment 896496 [details]
File: limits
Comment 8 Pavel Mlčoch 2014-05-16 18:17:23 UTC 
Created attachment 896497 [details]
File: maps
Comment 9 Pavel Mlčoch 2014-05-16 18:17:25 UTC 
Created attachment 896498 [details]
File: open_fds
Comment 10 Pavel Mlčoch 2014-05-16 18:17:28 UTC 
Created attachment 896499 [details]
File: proc_pid_status
Comment 11 Pavel Mlčoch 2014-05-16 18:17:30 UTC 
Created attachment 896500 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-05-19 06:14:39 UTC 
Thanks for a bug report. I would guess from the backtrace that there happened some memory corruption, like when some part of the code accesses an already freed memory, but I do not see in the backtrace how that could happen. The problem is that such memory corruptions can happen in one time and strike later.

Do you have any steps of clues how to reproduce this, please? Basically anything what could help to identify the cause.
Comment 13 Pavel Mlčoch 2014-05-19 11:43:15 UTC 
I can't help. This crashes is without user assistance.
Comment 14 Fedora Admin XMLRPC Client 2014-09-04 14:30:31 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 15 Fedora End Of Life 2015-05-29 11:52:15 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 16 Fedora End Of Life 2015-06-29 20:39:54 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.