Bug 646439

Summary: [abrt] fontforge-20090923-3.fc13: AW_ScriptSerifChecker: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dave Jeffery <david.richard.jeffery>
Component: fontforgeAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: fonts-bugs, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:82c18fc2880bbf791188449b321ec6c90f6090c5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 11:13:59 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
FontForge .sfd file for Washington font none

Description Dave Jeffery 2010-10-25 12:37:55 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: fontforge '/home/kecskebak/Projects/washington/Washington (copy).sfd'
component: fontforge
crash_function: AW_ScriptSerifChecker
executable: /usr/bin/fontforge
kernel: 2.6.34.7-61.fc13.i686
package: fontforge-20090923-3.fc13
rating: 4
reason: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: 1. Tried to autokern a font. Crash.
time: 1288009800
uid: 500

Comment 1 Dave Jeffery 2010-10-25 12:38:00 UTC
Created attachment 455526 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-10-25 17:21:57 UTC
Is the font you are operating on free? Could you attach it or let us know where we could download it?

There was some discussion recently on the upstream list about a autokern crash.

Comment 3 Dave Jeffery 2010-10-26 02:27:01 UTC
Created attachment 455665 [details]
FontForge .sfd file for Washington font

This is the (half finished) font I was working on when I encountered the crash - it's called "Washington" and is based on a scan out of an old BBC typeface catalogue from the early 1950s.

The font is free, I'm planning to release it under the SIL Open Font Licence.

What I did when the crash occurred was first try setting both bearings, and then auto kerning. If you do those two operations a few times changing the bearings and the kerning each time you should be able to recreate the crash.

Comment 4 Bug Zapper 2011-05-31 10:41:43 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-28 11:13:59 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.