Bug 885198

Summary: [abrt] evolution-3.6.2-3.fc18: ssl_FdIsBlocking: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: tigranes
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: John_Sauter, lucilanga, mbarnes, mcrha, murray.alex
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:09c8f1e95a8ad6d5196ad9f5680b94d68d6ec6cc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-10 11:23:30 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description tigranes 2012-12-07 18:32:43 UTC 
Description of problem:
Evolution crashed while opening. I did nothing unusual during the previous session, only checked my email and exited. That was perhaps an hour before I tried to launch it again, and it crashed.

Version-Release number of selected component:
evolution-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        evolution
crash_function: ssl_FdIsBlocking
executable:     /usr/bin/evolution
kernel:         3.6.7-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 ssl_FdIsBlocking at sslsock.c:2359
 #2 ssl_SocketIsBlocking at sslsock.c:2368
 #3 SSL_ForceHandshake at sslsecur.c:362
 #4 rehandshake_ssl at camel-tcp-stream-ssl.c:785
 #6 tcp_stream_ssl_connect at camel-tcp-stream-ssl.c:833
 #7 camel_tcp_stream_connect at camel-tcp-stream.c:111
 #8 network_service_connect_sync at camel-network-service.c:108
 #9 imapx_connect_to_server at camel-imapx-server.c:3520
 #10 imapx_reconnect at camel-imapx-server.c:3858
 #11 camel_imapx_server_connect at camel-imapx-server.c:6552

Potential duplicate: bug 849473
Comment 1 tigranes 2012-12-07 18:32:46 UTC 
Created attachment 659533 [details]
File: backtrace
Comment 2 tigranes 2012-12-07 18:32:47 UTC 
Created attachment 659534 [details]
File: cgroup
Comment 3 tigranes 2012-12-07 18:32:49 UTC 
Created attachment 659535 [details]
File: core_backtrace
Comment 4 tigranes 2012-12-07 18:32:52 UTC 
Created attachment 659536 [details]
File: dso_list
Comment 5 tigranes 2012-12-07 18:32:55 UTC 
Created attachment 659537 [details]
File: environ
Comment 6 tigranes 2012-12-07 18:32:57 UTC 
Created attachment 659538 [details]
File: limits
Comment 7 tigranes 2012-12-07 18:33:00 UTC 
Created attachment 659539 [details]
File: maps
Comment 8 tigranes 2012-12-07 18:33:03 UTC 
Created attachment 659540 [details]
File: open_fds
Comment 9 tigranes 2012-12-07 18:33:05 UTC 
Created attachment 659541 [details]
File: proc_pid_status
Comment 10 tigranes 2012-12-07 18:33:06 UTC 
Created attachment 659542 [details]
File: var_log_messages
Comment 11 Milan Crha 2012-12-10 11:23:30 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. I'm updating corresponding upstream bug report.

*** This bug has been marked as a duplicate of bug 849473 ***
Comment 12 Milan Crha 2012-12-17 14:19:22 UTC 
*** Bug 887779 has been marked as a duplicate of this bug. ***
Comment 13 Milan Crha 2013-03-22 11:10:12 UTC 
*** Bug 924449 has been marked as a duplicate of this bug. ***