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: folder_item_get_msginfo_by_msgid executable: /usr/bin/claws-mail kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 folder_item_get_msginfo_by_msgid at folder.c:2810 #1 procmsg_msg_has_flagged_parent_real at procmsg.c:2138 #2 procmsg_msg_has_flagged_parent at procmsg.c:2186 #3 procmsg_msg_has_marked_parent at procmsg.c:2198 #4 update_folder_msg_counts at procmsg.c:1940 #5 procmsg_msginfo_unset_flags at procmsg.c:2059 #6 msginfo_mark_as_read at summaryview.c:3523 #7 msginfo_mark_as_read_timeout at summaryview.c:3541 #13 gtk_main at gtkmain.c:1257 Potential duplicate: bug 711339
Created attachment 877407 [details] File: backtrace
Created attachment 877408 [details] File: cgroup
Created attachment 877409 [details] File: core_backtrace
Created attachment 877410 [details] File: dso_list
Created attachment 877411 [details] File: environ
Created attachment 877412 [details] File: exploitable
Created attachment 877413 [details] File: limits
Created attachment 877414 [details] File: maps
Created attachment 877415 [details] File: open_fds
Created attachment 877416 [details] File: proc_pid_status
Created attachment 877417 [details] File: var_log_messages
Probably fixed with http://git.claws-mail.org/?p=claws.git;a=commit;h=e240402b874071ffafe74aaffe60c177cb798567
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.