Version-Release number of selected component: vim-X11-8.0.1187-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: gvim -d /etc/sabnzbd/sabnzbd.conf /home/brian/.config/sabnzbd.conf /home/brian/.sabnzbd/sabnzbd.ini crash_function: getout executable: /usr/bin/gvim journald_cursor: s=65887db5d1bc4f80992ab48fe01dfa33;i=cd166;b=73291d695bd3424098d77d2c745837b4;m=182e0ff7cd0;t=55dcc280a42da;x=af4e938932d4a3e7 kernel: 4.13.5-200.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (1 frames) #4 getout at main.c:1543
Created attachment 1355789 [details] File: backtrace
Created attachment 1355790 [details] File: cgroup
Created attachment 1355791 [details] File: core_backtrace
Created attachment 1355792 [details] File: cpuinfo
Created attachment 1355793 [details] File: dso_list
Created attachment 1355794 [details] File: environ
Created attachment 1355795 [details] File: limits
Created attachment 1355796 [details] File: maps
Created attachment 1355797 [details] File: open_fds
Created attachment 1355798 [details] File: proc_pid_status
Created attachment 1355799 [details] File: var_log_messages
Hi Brian, thank you for reporting this issue. When did crash happened?
I'm not exactly sure. Sometime in the last couple of weeks perhaps.
Oh of course. The var_log_messages attachment 1355799 [details] tells us: Nov 12 12:05:09 pc.interlinx.bc.ca audit[32133]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=32133 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1 Nov 12 12:05:09 pc.interlinx.bc.ca audit[14953]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=14953 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1 Nov 12 12:05:09 pc.interlinx.bc.ca audit[10986]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=10986 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1 Nov 12 12:05:09 pc.interlinx.bc.ca audit[13449]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=13449 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1 Nov 12 12:05:09 pc.interlinx.bc.ca audit[19891]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=19891 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1 Nov 12 12:05:09 pc.interlinx.bc.ca audit[21484]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=21484 comm="gvim" exe="/usr/bin/gvim" sig=11 res=1
I'm sorry - the right question is: What were you doing, when this crash happened?
Unfortunately, I don't recall.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.