Bug 713165 - [abrt] bluefish-2.0.3-3.fc14: bmark_clean_for_doc: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Summary: [abrt] bluefish-2.0.3-3.fc14: bmark_clean_for_doc: Process /usr/bin/bluefish ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: bluefish
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e8d73a94961f2b5d87048ba01af...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-14 14:17 UTC by Olostech
Modified: 2012-02-16 18:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-16 18:57:24 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (23.49 KB, text/plain)
2011-06-14 14:17 UTC, Olostech 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 652633 0 None None None Never

Description Olostech 2011-06-14 14:17:10 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 24053 bytes
cmdline: bluefish
component: bluefish
Attached file: coredump, 141344768 bytes
crash_function: bmark_clean_for_doc
executable: /usr/bin/bluefish
kernel: 2.6.35.12-88.fc14.x86_64
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: 1308060744
uid: 500

How to reproduce
-----
1. 
2.
3.
 .
Comment 1 Olostech 2011-06-14 14:17:13 UTC 
Created attachment 504685 [details]
File: backtrace
Comment 2 Paul Howarth 2011-06-15 09:44:48 UTC 
Can you remember what you were doing when this crash happened?

I have reported this crash upstream at:
https://bugzilla.gnome.org/show_bug.cgi?id=652633
Comment 3 Paul Howarth 2012-02-16 18:57:24 UTC 
Upstream thinks this is probably fixed in current code. If it happens again, we can open a new bug or reopen this one.
Note You need to log in before you can comment on or make changes to this bug.