Description of problem: Claws-mail crashed some time when I was away from keyboard and screen was locked. Version-Release number of selected component: claws-mail-3.9.3-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: claws-mail crash_function: g_malloc executable: /usr/bin/claws-mail kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 22482 Truncated backtrace: Thread no. 1 (7 frames) #2 g_malloc at gmem.c:104 #3 g_strconcat at gstrfuncs.c:589 #4 vcal_manager_get_event_file at vcal_manager.c:860 #5 vcal_manager_load_event at vcal_manager.c:1096 #6 vcal_get_events_list at vcal_folder.c:742 #7 vcal_meeting_alert_check at vcal_meeting_gtk.c:1860 #13 gtk_main at gtkmain.c:1257
Created attachment 884073 [details] File: backtrace
Created attachment 884074 [details] File: cgroup
Created attachment 884075 [details] File: core_backtrace
Created attachment 884076 [details] File: dso_list
Created attachment 884077 [details] File: environ
Created attachment 884078 [details] File: exploitable
Created attachment 884079 [details] File: limits
Created attachment 884080 [details] File: maps
Created attachment 884081 [details] File: open_fds
Created attachment 884082 [details] File: proc_pid_status
Created attachment 884083 [details] File: var_log_messages
Same response as in bug 1071327, albeit there has been an interesting series of commits upstream related to memory corruption caused by interrupting an IMAP session: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3145
claws-mail-3.10.0-1.fc20,claws-mail-plugins-3.10.0-1.fc20,libetpan-1.5-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/claws-mail-3.10.0-1.fc20,claws-mail-plugins-3.10.0-1.fc20,libetpan-1.5-1.fc20
claws-mail-3.10.0-1.fc19,claws-mail-plugins-3.10.0-1.fc19,libetpan-1.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/claws-mail-3.10.0-1.fc19,claws-mail-plugins-3.10.0-1.fc19,libetpan-1.5-1.fc19
Package claws-mail-3.10.0-1.fc19, claws-mail-plugins-3.10.0-1.fc19, libetpan-1.5-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing claws-mail-3.10.0-1.fc19 claws-mail-plugins-3.10.0-1.fc19 libetpan-1.5-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6774/claws-mail-3.10.0-1.fc19,claws-mail-plugins-3.10.0-1.fc19,libetpan-1.5-1.fc19 then log in and leave karma (feedback).
claws-mail-3.10.0-1.fc20, claws-mail-plugins-3.10.0-1.fc20, libetpan-1.5-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
claws-mail-plugins-3.11.1-1.fc19,claws-mail-3.11.1-2.fc19,libetpan-1.6-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/claws-mail-plugins-3.11.1-1.fc19,claws-mail-3.11.1-2.fc19,libetpan-1.6-1.fc19
claws-mail-plugins-3.11.1-1.fc20,claws-mail-3.11.1-2.fc20,libetpan-1.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/claws-mail-plugins-3.11.1-1.fc20,claws-mail-3.11.1-2.fc20,libetpan-1.6-1.fc20
claws-mail-plugins-3.11.1-1.fc21,claws-mail-3.11.1-2.fc21,libetpan-1.6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/claws-mail-plugins-3.11.1-1.fc21,claws-mail-3.11.1-2.fc21,libetpan-1.6-1.fc21
claws-mail-plugins-3.11.1-1.fc20, claws-mail-3.11.1-2.fc20, libetpan-1.6-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
claws-mail-plugins-3.11.1-1.fc21, claws-mail-3.11.1-2.fc21, libetpan-1.6-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
claws-mail-plugins-3.11.1-1.fc19, claws-mail-3.11.1-2.fc19, libetpan-1.6-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.