Bug 688061

Summary: [abrt] bluefish-2.0.3-2.fc13: file_checkNsave_cancel: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: isulic
Component: bluefishAssignee: Paul Howarth <paul>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:30a131104d87da08f9f1f6df7b468ab6b01b19f3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-16 08:57:10 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 isulic 2011-03-16 07:40:07 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/bluefish
component: bluefish
crash_function: file_checkNsave_cancel
executable: /usr/bin/bluefish
kernel: 2.6.34.8-68.fc13.i686
package: bluefish-2.0.3-2.fc13
rating: 4
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: Closing app
time: 1300261111
uid: 500
Comment 1 isulic 2011-03-16 07:40:10 UTC 
Created attachment 485666 [details]
File: backtrace
Comment 2 Paul Howarth 2011-03-16 08:57:10 UTC 
Please try bluefish-2.0.3-3.fc13 from updates-testing, which should prevent this from happening.

yum --enablerepo=updates-testing update bluefish

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