Hide Forgot
Description of problem: Two imap accounts. Changed the name/display name of one of them. There was a lot of disk I/O on the machine at the time. Have not been able to reproduce yet. 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.6-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_cmctree_is_viewable at gtkcmctree.c:3453 #1 gtk_cmctree_node_moveto at gtkcmctree.c:4574 #2 summary_select_node at summaryview.c:2258 #3 summary_show at summaryview.c:1568 #4 folderview_selected at folderview.c:2221 #9 gtk_cmctree_select at gtkcmctree.c:3903 #10 real_unselect_all at gtkcmctree.c:2881 #11 gtk_sctree_real_unselect_all at gtksctree.c:792 #12 select_row at gtksctree.c:383 #13 gtk_sctree_button_press at gtksctree.c:554
Created attachment 818353 [details] File: backtrace
Created attachment 818354 [details] File: cgroup
Created attachment 818355 [details] File: core_backtrace
Created attachment 818356 [details] File: dso_list
Created attachment 818357 [details] File: environ
Created attachment 818358 [details] File: exploitable
Created attachment 818359 [details] File: limits
Created attachment 818360 [details] File: maps
Created attachment 818361 [details] File: open_fds
Created attachment 818362 [details] File: proc_pid_status
Created attachment 818363 [details] File: var_log_messages
Interesting, but I can confirm it's not reproducible if simply renaming IMAP accounts within CM. gtkcmctree is an implementation by CM, but gtk2 in F20 and F19 is the same. The crash could also be a side-effect of earlier networking problems with remote IMAP access, however, and that's plagueing CM for a long time.
A new release of Claws Mail (and its dependency libetpan) is available for testing with Fedora 20 and Fedora 19: https://admin.fedoraproject.org/updates/search/claws Please allow for the time it takes for the packages to show up in the "updates-testing" repository and then to be picked up by the world-wide download mirror servers.
I haven't been able to reproduce it so this is likely a non-issue by now.