Bug 672721 - [abrt] bluefish-2.0.3-0.1.rc1.fc15: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Summary: [abrt] bluefish-2.0.3-0.1.rc1.fc15: Process /usr/bin/bluefish was killed by s...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: bluefish
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:46a84ddbe48c74cac2402b68eaa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-26 01:23 UTC by Luya Tshimbalanga
Modified: 2012-09-14 15:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-14 15:39:57 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (11.21 KB, text/plain)
2011-01-26 01:23 UTC, Luya Tshimbalanga 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Luya Tshimbalanga 2011-01-26 01:23:35 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: bluefish
comment: Bluefish crashed after saving a css file. Test done on LG LT20 laptop.
component: bluefish
executable: /usr/bin/bluefish
kernel: 2.6.37-2.fc15.i686
package: bluefish-2.0.3-0.1.rc1.fc15
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1296004898
uid: 500

How to reproduce
-----
1. Save css file
2.
3.
Comment 1 Luya Tshimbalanga 2011-01-26 01:23:36 UTC 
Created attachment 475311 [details]
File: backtrace
Comment 2 Paul Howarth 2011-01-31 16:18:35 UTC 
Did this just happen once or is it reproducible?
Comment 3 Luya Tshimbalanga 2011-01-31 19:10:20 UTC 
It happened once.
Comment 4 Paul Howarth 2011-03-14 14:35:00 UTC 
I've added this backtrace to upstream bug #643705, which is similar but not quite the same.
Comment 5 Paul Howarth 2012-09-14 15:39:57 UTC 
Upstream thinks this is probably fixed in 2.2.x (F-17 and above), and given that it hasn't happened again, either for you or anybody else, we'll believe them. Please reopen or raise a new ticket if it does happen again.
Note You need to log in before you can comment on or make changes to this bug.