Version-Release number of selected component: vim-enhanced-7.3.712-1.fc18 Additional info: backtrace_rating: 3 cmdline: vim recepty crash_function: may_core_dump executable: /usr/bin/vim kernel: 3.7.0-0.rc8.git0.1.fc19.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Dec 28 18:27:00 boosh abrt[28216]: Saved core dump of pid 27778 (/usr/bin/vim) to /var/spool/abrt/ccpp-2012-12-28-18:27:00-27778 (2514944 bytes) Truncated backtrace: Thread no. 1 (10 frames) #1 may_core_dump at os_unix.c:3166 #3 mch_exit at os_unix.c:3132 #4 getout at main.c:1466 #5 deathtrap at os_unix.c:1088 #7 eval7 at eval.c:5739 #8 eval6 at eval.c:4809 #9 eval5 at eval.c:4625 #10 eval4 at eval.c:4318 #11 eval3 at eval.c:4230 #12 eval1 at eval.c:4159 Potential duplicate: bug 835143
Created attachment 672981 [details] File: backtrace
Created attachment 672982 [details] File: cgroup
Created attachment 672983 [details] File: core_backtrace
Created attachment 672984 [details] File: dso_list
Created attachment 672985 [details] File: environ
Created attachment 672986 [details] File: limits
Created attachment 672987 [details] File: maps
Created attachment 672988 [details] File: open_fds
Created attachment 672989 [details] File: proc_pid_status
Created attachment 672990 [details] File: system_vimrc
Created attachment 672991 [details] File: user_vimrc
Steps to reproduce: 1. open the vim in gnome-terminal 2. do not exit from vim and close gnome-terminal 3. abrt will report this problem How reproducable: Not always, but quite often. backtrace_rating: 4 Package: vim-enhanced-7.3.712-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
vim was running in xterm. I closed the xterm through the window manager (i3). backtrace_rating: 4 cmdline: vim generic.tex crash_function: may_core_dump executable: /usr/bin/vim kernel: 3.8.11-200.fc18.x86_64 package: vim-enhanced-7.3.712-1.fc18 reason: Process /usr/bin/vim was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
please try vim-7.3.944-1.fc18 from updates-testing and see if that fixes this issue. Feel free to re-open this bugzila if the problem still exists with the updated vim.
vim crashed when I closed the konsole window it was running in. This is completely reproducible though I'm not sure it isn't expected behaviour. I have the following extensions installed: minibufexpl pep8 pydoc pyflakes-pathogen ropevim supertab reporter: libreport-2.1.6 backtrace_rating: 3 cmdline: vim partner.py crash_function: may_core_dump executable: /usr/bin/vim kernel: 3.9.11-200.fc18.x86_64 package: vim-enhanced-7.3.944-1.fc18 reason: Process /usr/bin/vim was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 500
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.