Version-Release number of selected component: evolution-3.28.5-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: evolution crash_function: WTF::String::utf8(WTF::ConversionMode) const executable: /usr/bin/evolution journald_cursor: s=b2462b34e86d43ef805c1ee012da0964;i=61974;b=9a8333dc2c5c42a491fbb370f2e06bb9;m=4dbd5a47;t=5735bcc8d01fe;x=ca285aa8278a48b kernel: 4.17.12-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 WTF::String::utf8(WTF::ConversionMode) const at /usr/src/debug/webkit2gtk3-2.20.4-1.fc28.x86_64/Source/WTF/wtf/text/WTFString.cpp:820 #1 WTF::String::utf8() const at /usr/src/debug/webkit2gtk3-2.20.4-1.fc28.x86_64/Source/WTF/wtf/text/WTFString.cpp:826 #2 WebCore::PasteboardHelper::fillSelectionData(WebCore::SelectionData const&, unsigned int, _GtkSelectionData*) at /usr/src/debug/webkit2gtk3-2.20.4-1.fc28.x86_64/Source/WebCore/platform/gtk/SelectionData.h:38
Created attachment 1475729 [details] File: backtrace
Created attachment 1475730 [details] File: cgroup
Created attachment 1475731 [details] File: core_backtrace
Created attachment 1475732 [details] File: cpuinfo
Created attachment 1475733 [details] File: dso_list
Created attachment 1475734 [details] File: environ
Created attachment 1475735 [details] File: exploitable
Created attachment 1475736 [details] File: limits
Created attachment 1475737 [details] File: maps
Created attachment 1475738 [details] File: mountinfo
Created attachment 1475739 [details] File: open_fds
Created attachment 1475740 [details] File: proc_pid_status
Thanks for a bug report. This looks like an issue in webkit2gtk3, thus I move this there. It looks like you've been dragging a text selection either from a message preview, or message composer, or any other preview panel of evolution, or other places where is WebKitGTK+ used. Do you recall what you've been doing when the crash happened, please? Having some steps or at least hints on the things which had been done before the crash helps significantly to investigate the crash.
*** This bug has been marked as a duplicate of bug 1541220 ***