Description of problem: Reading GMAIL over IMAP. clicked on a message and BOOM Version-Release number of selected component: claws-mail-3.9.2-7.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: claws-mail crash_function: gtk_cmctree_is_viewable executable: /usr/bin/claws-mail kernel: 3.11.7-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (7 frames) #0 gtk_cmctree_is_viewable at gtkcmctree.c:3453 #1 tree_draw_node at gtkcmctree.c:2708 #2 gtk_cmctree_node_set_foreground at gtkcmctree.c:4494 #3 summary_set_row_marks at summaryview.c:3829 #4 msginfo_mark_as_read at summaryview.c:3524 #5 msginfo_mark_as_read_timeout at summaryview.c:3541 #11 gtk_main at gtkmain.c:1257 Potential duplicate: bug 928125
Created attachment 830290 [details] File: backtrace
Created attachment 830291 [details] File: cgroup
Created attachment 830292 [details] File: core_backtrace
Created attachment 830293 [details] File: dso_list
Created attachment 830294 [details] File: environ
Created attachment 830295 [details] File: exploitable
Created attachment 830296 [details] File: limits
Created attachment 830297 [details] File: maps
Created attachment 830298 [details] File: open_fds
Created attachment 830299 [details] File: proc_pid_status
Created attachment 830300 [details] File: var_log_messages
> Reading GMAIL over IMAP. clicked on a message and BOOM Here you were supposed to mention whether the problem is reproducible (and how often it occurs). It is indeed a dupe of bug 928125. The crash is related to marking a message as read, but it could be just a side-effect because IMAP is involved (which in Claws Mail can lead to side-effects if encoutering networking problems). Please show the output of these commands: grep mark_as_read ~/.claws-mail/clawsrc grep layout ~/.claws-mail/clawsrc grep io_timeout ~/.claws-mail/clawsrc
Sorry - just brain-dead pounding through the ABRT prompts. I've only seen this crash once and have not tried to repro. cbox:ccb1001 grep mark_as_read ~/.claws-mail/clawsrc mark_as_read_on_new_window=0 mark_as_read_delay=4 mark_as_read=1 cbox:ccb1002 grep layout ~/.claws-mail/clawsrc layout_mode=0 cbox:ccb1003 grep io_timeout ~/.claws-mail/clawsrc io_timeout_secs=60
In an attempt at reproducing it, I've been running Claws Mail with mark_as_read_delay=4 for a long time, but couldn't reproduce anything like that with multiple IMAP servers including Google Mail.
There has been a series of interesting commits upstream related to memory corruption, memory leaks and also mark_as_read callback. It may or may not fix this in a future release: http://git.claws-mail.org/?p=claws.git;a=commitdiff;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.