Description of problem: listed messages Version-Release number of selected component: evolution-3.9.91-2.fc20 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: evolution crash_function: g_slist_last executable: /usr/bin/evolution kernel: 3.11.0-3.fc20.x86_64 runlevel: unknown uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_slist_last at gslist.c:845 #1 g_slist_append at gslist.c:230 #2 g_main_context_new at gmain.c:620 #3 async_closure_new at camel-service.c:131 #4 camel_service_connect_sync at camel-service.c:1638 #5 camel_folder_synchronize_sync at camel-folder.c:4311 #6 refresh_folders_exec at mail-send-recv.c:1054 #7 mail_msg_proxy at mail-mt.c:422 #9 g_thread_proxy at gthread.c:798 #11 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Created attachment 794861 [details] File: backtrace
Created attachment 794862 [details] File: cgroup
Created attachment 794863 [details] File: core_backtrace
Created attachment 794864 [details] File: dso_list
Created attachment 794865 [details] File: environ
Created attachment 794866 [details] File: exploitable
Created attachment 794867 [details] File: limits
Created attachment 794868 [details] File: maps
Created attachment 794869 [details] File: open_fds
Created attachment 794870 [details] File: proc_pid_status
Created attachment 794871 [details] File: var_log_messages
Thanks for a bug report. Based on your backtrace, this is either caused by a memory corruption or there is some bug in g_main_context_new() function. Because this comes from glib2, I'm moving this there for further investigation. I see you have installed glib2-2.37.7-1.fc20.x86_64. By any chance, are you able to reproduce this reliably, after opening certain messages in certain order?
(In reply to Milan Crha from comment #12) > Thanks for a bug report. Based on your backtrace, this is either caused by a > memory corruption or there is some bug in g_main_context_new() function. > Because this comes from glib2, I'm moving this there for further > investigation. > > I see you have installed glib2-2.37.7-1.fc20.x86_64. > > By any chance, are you able to reproduce this reliably, after opening > certain messages in certain order? unfortunately, no :(
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.
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.