Description of problem: Launched Geary (e-mail application) to send a message. After inputting the recipient e-mail address and subject, proceeded to paste a link from the web browser, when notification of the crash displayed. Version-Release number of selected component: webkit2gtk3-2.20.2-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 1 53 crash_function: geary_web_extension_execute_script executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess journald_cursor: s=4c15eab3a57a4ca4b5cc4c749bade99f;i=15838;b=6b2889eb0bdb4c20bf9aac501bf6688a;m=16c08475;t=56d1cabdcda9f;x=a2e5671ac27f85cf kernel: 4.16.11-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #6 geary_web_extension_execute_script at /usr/src/debug/geary-0.12.2-1.fc28.x86_64/src/client/web-process/web-process-extension.vala:144 #7 geary_web_extension_selection_changed at /usr/include/stdlib.h:363 #8 __lambda5_ at /usr/src/debug/geary-0.12.2-1.fc28.x86_64/src/client/web-process/web-process-extension.vala:47 #9 ___lambda5__webkit_web_editor_selection_changed at /usr/src/debug/geary-0.12.2-1.fc28.x86_64/src/client/web-process/web-process-extension.vala:46
Created attachment 1441921 [details] File: backtrace
Created attachment 1441922 [details] File: cgroup
Created attachment 1441923 [details] File: core_backtrace
Created attachment 1441924 [details] File: cpuinfo
Created attachment 1441925 [details] File: dso_list
Created attachment 1441926 [details] File: environ
Created attachment 1441927 [details] File: limits
Created attachment 1441928 [details] File: maps
Created attachment 1441929 [details] File: mountinfo
Created attachment 1441930 [details] File: open_fds
Created attachment 1441931 [details] File: proc_pid_status
Similar problem has been detected: Launched Geary to send an e-mail, compose screen appeared, but portion of window where message body is typed, was inaccessible. Then the crash reporter launched. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 1 40 crash_function: geary_web_extension_execute_script executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess journald_cursor: s=4c15eab3a57a4ca4b5cc4c749bade99f;i=4e1cd;b=c8261c6cc2994ee6a13f6434251ea8d9;m=dc58428a;t=570c36e9fb36d;x=68702954fe1c8ad0 kernel: 4.17.3-200.fc28.x86_64 package: webkit2gtk3-2.20.3-1.fc28 reason: WebKitWebProcess killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This is memory corruption, so a backtrace is not useful. My normal recommendation for these issues is to try to catch it in valgrind, but that's not going to work for the web process. It will require an asan build to track down.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.