Bug 1477361 - [abrt] evolution: g_io_stream_get_input_stream(): evolution killed by signal 11
[abrt] evolution: g_io_stream_get_input_stream(): evolution killed by signal 11
Status: NEW
Product: Fedora
Classification: Fedora
Component: evolution-ews (Show other bugs)
27
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Milan Crha
Fedora Extras Quality Assurance
https://retrace.fedoraproject.org/faf...
abrt_hash:bef6d19d53b28cefc338564abbf...
:
: 1541154 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-01 17:25 EDT by Pavel Roskin
Modified: 2018-02-07 17:21 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (81.43 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: cgroup (195 bytes, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: core_backtrace (43.87 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: cpuinfo (1.35 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: dso_list (25.54 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: environ (1.88 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: exploitable (82 bytes, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: limits (1.29 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: maps (123.02 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: open_fds (4.11 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details
File: var_log_messages (3.30 KB, text/plain)
2017-08-01 17:25 EDT, Pavel Roskin
no flags Details

  None (edit)
Description Pavel Roskin 2017-08-01 17:25:30 EDT
Version-Release number of selected component:
evolution-3.24.4-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        evolution
crash_function: g_io_stream_get_input_stream
executable:     /usr/bin/evolution
journald_cursor: s=2b427e5c155c4c6ebb2ea03017e4893b;i=d342c;b=54615f1f74274aefaa1d155ae09f1b98;m=23afbe775;t=555b78e9c5961;x=5ab77fe17b286909
kernel:         4.11.11-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_io_stream_get_input_stream at giostream.c:231
 #1 new_iostate at soup-message-io.c:1185
 #2 soup_message_io_client at soup-message-io.c:1215
 #3 soup_message_send_request at soup-message-client-io.c:161
 #4 soup_connection_send_request at soup-connection.c:708
 #5 soup_session_send_queue_item at soup-session.c:1326
 #6 soup_session_process_queue_item at soup-session.c:1987
 #7 soup_session_real_send_message at soup-session.c:2218
 #8 e_ews_notification_unsubscribe_folder_sync at /usr/src/debug/evolution-ews-3.24.4/src/server/e-ews-notification.c:485
 #9 e_ews_notification_get_events_thread at /usr/src/debug/evolution-ews-3.24.4/src/server/e-ews-notification.c:882
Comment 1 Pavel Roskin 2017-08-01 17:25:35 EDT
Created attachment 1307809 [details]
File: backtrace
Comment 2 Pavel Roskin 2017-08-01 17:25:36 EDT
Created attachment 1307810 [details]
File: cgroup
Comment 3 Pavel Roskin 2017-08-01 17:25:37 EDT
Created attachment 1307811 [details]
File: core_backtrace
Comment 4 Pavel Roskin 2017-08-01 17:25:38 EDT
Created attachment 1307812 [details]
File: cpuinfo
Comment 5 Pavel Roskin 2017-08-01 17:25:38 EDT
Created attachment 1307813 [details]
File: dso_list
Comment 6 Pavel Roskin 2017-08-01 17:25:39 EDT
Created attachment 1307814 [details]
File: environ
Comment 7 Pavel Roskin 2017-08-01 17:25:40 EDT
Created attachment 1307815 [details]
File: exploitable
Comment 8 Pavel Roskin 2017-08-01 17:25:41 EDT
Created attachment 1307816 [details]
File: limits
Comment 9 Pavel Roskin 2017-08-01 17:25:42 EDT
Created attachment 1307817 [details]
File: maps
Comment 10 Pavel Roskin 2017-08-01 17:25:42 EDT
Created attachment 1307818 [details]
File: open_fds
Comment 11 Pavel Roskin 2017-08-01 17:25:43 EDT
Created attachment 1307819 [details]
File: proc_pid_status
Comment 12 Pavel Roskin 2017-08-01 17:25:44 EDT
Created attachment 1307820 [details]
File: var_log_messages
Comment 13 Milan Crha 2017-08-02 00:56:28 EDT
Thanks for a bug report. I see from the backtrace that the crash happened when evolution-ews tried to unsubscribe an event listener, which is used to receive notifications about changes on the server. There had been also something going on in painting, I guess one of the accounts had been connecting or something, but the other threads do not look like that. The var_log_messages file shows runtime warnings related to libsoup, thus most likely also connected to evolution-ews.

I'm not sure how to reproduce this. Did it happen for the first time for you, or you see this regularly? Eventually after any particular action? It can be even a connection state change, like when switching networks or anything like that.
Comment 14 Pavel Roskin 2017-08-02 15:16:17 EDT
I've been using Evolution with Exchange for months on that system, back when Fedora 26 was in Beta. There were no changes to Evolution configuration in the days before the crash. I don't remember Evolution crashing on the system before. That was a one-off event. I went to lunch while Evolution was open. When I came back, the system was locked (which is normal), and there was a message that Evolution had crashed. I'm using the default GNOME desktop on X11 (XDG_SESSION_TYPE=x11).

I have no idea how to reproduce the crash, but I'll keep Evolution running while going to lunch :)
Comment 15 Milan Crha 2017-08-03 00:25:22 EDT
Thanks for the update. I'll keep the bug open for the time being, though I understand this could be just some corner-case issue, thus very hard to reproduce.
Comment 16 Milan Crha 2018-02-06 04:12:42 EST
*** Bug 1541154 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.