Bug 669822 - [abrt] vim-enhanced-2:7.3.056-1.fc14: kill: Process /usr/bin/vim was killed by signal 11 (SIGSEGV)
Summary: [abrt] vim-enhanced-2:7.3.056-1.fc14: kill: Process /usr/bin/vim was killed b...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:67fcd6f63857491367b7ffe5db7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 21:34 UTC by rdesfo
Modified: 2011-08-29 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-29 12:48:39 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (10.01 KB, text/plain)
2011-01-14 21:34 UTC, rdesfo
no flags Details

Description rdesfo 2011-01-14 21:34:49 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: vim -S /home/ryan/Documents/vim/notebook.vim
comment: The file was owned by me and something changed with the update.  Caused system to crash and had to run 'fsck' to be able to log in again
component: vim
crash_function: kill
executable: /usr/bin/vim
kernel: 2.6.35.10-74.fc14.i686
package: vim-enhanced-2:7.3.056-1.fc14
rating: 4
reason: Process /usr/bin/vim was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295036570
uid: 500

How to reproduce
-----
1. opened vim
2. ran an update ( su -c 'yum update' )
3. alerted that I only had read only access

Comment 1 rdesfo 2011-01-14 21:34:51 UTC
Created attachment 473593 [details]
File: backtrace

Comment 2 P. Ignacio Q. 2011-02-18 01:58:39 UTC
Package: vim-enhanced-2:7.3.056-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.closed the gnome-terminal
2.
3.


Comment
-----
Vim opened and then close the gnome-terminal

Comment 3 Karsten Hopp 2011-08-29 12:48:39 UTC
vim-7.3.289-1.fc14 will be in f14-updates-testing soon. Please install that new version and check if it fixes your issues as it contains many fixes, including some segmentation faults.


Note You need to log in before you can comment on or make changes to this bug.