Description of problem: I clicked the button to go offline. Version-Release number of selected component: evolution-3.28.1-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: evolution crash_function: g_io_stream_get_input_stream executable: /usr/bin/evolution journald_cursor: s=33b0ccdfd4934679b811dbc2df8d05d6;i=1edf7;b=853a3605bdb7462fb1013b8ae6c1591a;m=a38c6a61;t=56b48309b7e3b;x=c763ae143d800c2b kernel: 4.16.5-300.fc28.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:1189 #2 soup_message_io_client at soup-message-io.c:1219 #3 soup_message_send_request at soup-message-client-io.c:161 #4 soup_connection_send_request at soup-connection.c:718 #5 soup_session_send_queue_item at soup-session.c:1338 #6 soup_session_process_queue_item at soup-session.c:2005 #7 soup_session_real_send_message at soup-session.c:2236 #8 e_ews_notification_unsubscribe_folder_sync at /usr/src/debug/evolution-ews-3.28.1-1.fc28.x86_64/src/server/e-ews-notification.c:439 #9 e_ews_notification_get_events_thread at /usr/src/debug/evolution-ews-3.28.1-1.fc28.x86_64/src/server/e-ews-notification.c:836 Potential duplicate: bug 1477361
Created attachment 1430531 [details] File: backtrace
Created attachment 1430532 [details] File: cgroup
Created attachment 1430533 [details] File: core_backtrace
Created attachment 1430534 [details] File: cpuinfo
Created attachment 1430535 [details] File: dso_list
Created attachment 1430536 [details] File: environ
Created attachment 1430537 [details] File: exploitable
Created attachment 1430538 [details] File: limits
Created attachment 1430539 [details] File: maps
Created attachment 1430540 [details] File: mountinfo
Created attachment 1430541 [details] File: open_fds
Created attachment 1430542 [details] File: proc_pid_status
Created attachment 1430543 [details] File: var_log_messages
Thanks for a bug report. A very similar crash had been filled already, thus I mark this as a duplicate of it. I always thought this is due to an unexpected disconnect from the network, but the "go offline" button is nothing unexpected, neither the network itself is really offline. *** This bug has been marked as a duplicate of bug 1477361 ***