Version-Release number of selected component: claws-mail-3.9.3-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: claws-mail crash_function: _cairo_xlib_surface_create_internal executable: /usr/bin/claws-mail kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _cairo_xlib_surface_create_internal at cairo-xlib-surface.c:1771 #3 _cairo_xlib_surface_create_similar at cairo-xlib-surface.c:321 #4 _cairo_surface_create_scratch at cairo-surface.c:877 #5 surface_source at cairo-xlib-source.c:1006 #6 _cairo_xlib_source_create_for_pattern at cairo-xlib-source.c:1141 #7 composite_aligned_boxes at cairo-traps-compositor.c:1292 #8 clip_and_composite_boxes at cairo-traps-compositor.c:1786 #9 _cairo_traps_compositor_fill at cairo-traps-compositor.c:2231 #10 _cairo_compositor_fill at cairo-compositor.c:203 #11 _cairo_xlib_surface_fill at cairo-xlib-surface.c:1646
Created attachment 850783 [details] File: backtrace
Created attachment 850784 [details] File: cgroup
Created attachment 850785 [details] File: core_backtrace
Created attachment 850786 [details] File: dso_list
Created attachment 850787 [details] File: environ
Created attachment 850788 [details] File: exploitable
Created attachment 850789 [details] File: limits
Created attachment 850790 [details] File: maps
Created attachment 850791 [details] File: open_fds
Created attachment 850792 [details] File: proc_pid_status
Created attachment 850793 [details] File: var_log_messages
#1 0x00007f83c1b6a00c in __GI___libc_malloc (bytes=816) at malloc.c:2859 Memory corruption somewhere [earlier], with the crash in Cairo likely only being a side-effect. If you don't have any ideas about reproducibility, not much can be done about it.
> Architecture Count > x86_64 1 Since you've not entered any details about reproducibility, there is nothing that can be done about this crash. Please note that a few key details are needed almost always (unless the backtrace points at exactly the place where it can be concluded what has gone wrong). Is the crash reproducible? And how? If it isn't, how often has it crashed? A couple of crashes of Claws Mail are just side-effects (caused by memory corruption and/or race conditions letting the code work with pointers to freed data), i.e. it can crash in arbitrary places. Recently, there have been several bug-fixes upstream that will stop some of those side-effects.
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.