Version-Release number of selected component: evolution-data-server-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: __pthread_mutex_lock executable: /usr/libexec/evolution-addressbook-factory kernel: 3.7.2-201.fc18.i686 remote_result: NOTFOUND uid: 1000 var_log_messages: Jan 23 13:29:32 lara abrt[1905]: Saved core dump of pid 1884 (/usr/libexec/evolution-addressbook-factory) to /var/spool/abrt/ccpp-2013-01-23-13:29:29-1884 (111472640 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 __pthread_mutex_lock at pthread_mutex_lock.c:50 #1 gnutls_system_mutex_lock at system.c:197 #2 mutex_init at ath.c:132 #3 _gcry_ath_mutex_lock at ath.c:186 #4 lock_fsm at fips.c:225 #5 _gcry_inactivate_fips_mode at fips.c:305 #6 _gcry_set_allocation_handler at global.c:705 #7 gcry_set_allocation_handler at visibility.c:1336 #8 egg_libgcrypt_initialize at egg-libgcrypt.c:109 #9 gcr_secret_exchange_class_init at gcr-secret-exchange.c:872
Created attachment 685868 [details] File: backtrace
Created attachment 685869 [details] File: build_ids
Created attachment 685870 [details] File: cgroup
Created attachment 685871 [details] File: core_backtrace
Created attachment 685872 [details] File: dso_list
Created attachment 685873 [details] File: environ
Created attachment 685874 [details] File: limits
Created attachment 685875 [details] File: maps
Created attachment 685876 [details] File: open_fds
Created attachment 685877 [details] File: proc_pid_status
Thanks for a bug report. This seems to happen during gcr's initialization, where I do not see anything directly related to evolution, when in passes only a valid string to the gcr_secret_exchange_new() function, thus I'm moving this to gcr itself, for further investigation.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.