Bug 657665

Summary: [abrt] vim-X11-2:7.3.056-1.fc14: gtk_file_system_model_sort: Process /usr/bin/gvim was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Ed Marshall <esm>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dtardon, karsten
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d97d0a648ed407c4c483e8527d000ab23ffe83e0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-07 05:42:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Ed Marshall 2010-11-27 02:19:45 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gvim sh2.py
comment: This hasn't been reproducable, unfortunately; it only happened once.
component: vim
crash_function: gtk_file_system_model_sort
executable: /usr/bin/gvim
kernel: 2.6.35.6-48.fc14.i686
package: vim-X11-2:7.3.056-1.fc14
rating: 4
reason: Process /usr/bin/gvim was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1290821370
uid: 500

How to reproduce
-----
1. Opened a (python, in case syntax highlighting matters) file in gvim.
2. Opened a second (also python) file in a new tab in gvim (used "File|Open Tab...", rather than ":newtab").
3. Crash.
Comment 1 Ed Marshall 2010-11-27 02:19:49 UTC 
Created attachment 463195 [details]
File: backtrace
Comment 2 David Tardon 2010-12-07 05:42:59 UTC 

*** This bug has been marked as a duplicate of bug 603781 ***