Red Hat Bugzilla – Bug 587197
[abrt] crash in vim-X11-2:7.2.411-1.fc12: Process /usr/bin/gvim was killed by signal 11 (SIGSEGV)
Last modified: 2010-11-04 07:36:14 EDT
abrt 1.0.9 detected a crash.
Attached file: backtrace
cmdline: gvim Data_Provider.cc
comment: Crash when closing window (so priority not that high).
reason: Process /usr/bin/gvim was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Created attachment 410062 [details]
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
closing this as there is vim-7.3-29 in f12-updates with lots of fixes, at least one of them related to closing gvim windows:
- crash in GUI when closing the last window in a tabpage
*** Bug 578914 has been marked as a duplicate of this bug. ***
*** Bug 582360 has been marked as a duplicate of this bug. ***
*** Bug 549646 has been marked as a duplicate of this bug. ***
*** Bug 552260 has been marked as a duplicate of this bug. ***
*** Bug 570438 has been marked as a duplicate of this bug. ***