Bug 717174

Summary: [abrt] bluefish-2.0.3-3.fc14: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ulrich Walczak <ulrich>
Component: bluefishAssignee: Paul Howarth <paul>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f47e9cbb658e571b014d842caffb26d234af5a33
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-16 16:49:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Ulrich Walczak 2011-06-28 09:26:58 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 23293 bytes
cmdline: bluefish /home/Uli/Desktop/crowleyf.html
component: bluefish
Attached file: coredump, 70152192 bytes
crash_function: IA__gtk_text_buffer_get_insert
executable: /usr/bin/bluefish
kernel: 2.6.35.13-92.fc14.i686.PAE
package: bluefish-2.0.3-3.fc14
rating: 4
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1309248395
uid: 500

How to reproduce
-----
1.no idea, just happened
2.
3.
Comment 1 Ulrich Walczak 2011-06-28 09:27:01 UTC 
Created attachment 510228 [details]
File: backtrace
Comment 2 Paul Howarth 2011-07-06 14:52:22 UTC 
I have reported this crash upstream at:

https://bugzilla.gnome.org/show_bug.cgi?id=654091
Comment 3 Paul Howarth 2012-02-15 16:55:14 UTC 
Upstream thinks this is probably fixed in current code. Have you seen any repeat of this? Are you still running Fedora 14?
Comment 4 Ulrich Walczak 2012-02-15 19:22:05 UTC 
no, I don't run fedora 14 any more. I run now fedora 16, and bluefish isn't yet installed.
Comment 5 Paul Howarth 2012-02-16 16:49:16 UTC 
OK, let's assume upstream has indeed fixed it then and we can open a new bug (or re-open this one) if it happens again.