Bug 572678

Summary: [abrt] crash in gedit-1:2.29.7-1.fc13: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joel <hundred17>
Component: geditAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:9e10b17151b70175bd1878d533041a8e203911d8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-09 00:56:40 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 Joel 2010-03-11 20:22:12 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gedit /home/joel/Desktop/meeting_minutes.txt
comment: Just make a new empty file, and try to open it with gedit.
component: gedit
executable: /usr/bin/gedit
kernel: 2.6.33-1.fc13.x86_64
package: gedit-1:2.29.7-1.fc13
rating: 4
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)

How to reproduce
-----
1.Create new empty text file
2.Open it with gedit
3.Crash!
Comment 1 Joel 2010-03-11 20:22:14 UTC 
Created attachment 399442 [details]
File: backtrace
Comment 2 Joel 2010-04-02 18:30:06 UTC 
This hasn't been an issue for a while with Fedora 13.  I can say with certainty that gedit-2.29.8-2.fc13.x86_64 doesn't have the issue.