Bug 572427

Summary: [abrt] crash in fontforge-20090622-2.fc12: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Caius Chance <K9>
Component: fontforgeAssignee: Kevin Fenzi <kevin>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fonts-bugs, kevin, paul, roozbeh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:76dd7d152233d7934b4bb42e08385d8ac4cb7e3b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-03 15:25:40 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 Caius Chance 2010-03-11 06:54:26 UTC 
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: fontforge
component: fontforge
executable: /usr/bin/fontforge
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: fontforge-20090622-2.fc12
rating: 4
reason: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Open a font file by File > Open or on command line.
2. Hint > edit cvt table.
3. Expand the cvt table window.
4. It crashed.
Comment 1 Caius Chance 2010-03-11 06:54:29 UTC 
Created attachment 399264 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-03-11 17:10:44 UTC 
This is reproducable anytime via the above info? 

I will report this upstream. Unless you would like to do so to the fontforge-devel list?

Thanks for the report!
Comment 3 Caius Chance 2010-03-12 00:32:49 UTC 
(In reply to comment #2)
> This is reproducable anytime via the above info? 

I have tried more than 3 times on my machine yesterday. It was at the latest yum'ed state.

> I will report this upstream. Unless you would like to do so to the
> fontforge-devel list?

Please do. :)

> Thanks for the report!    

Thank you, too.
Comment 4 Kevin Fenzi 2010-07-04 19:07:19 UTC 
I don't see this anymore in newer fontforge versions. 

Can you confirm that it's fixed for you now?
Comment 5 Paul Flo Williams 2010-07-13 11:34:06 UTC 
See also bug 610168.

From that bug, fontforge-20090923-3.fc13 still has problem, but your latest scratch build (below), from the 20100501 sources, no longer has this problem.

http://koji.fedoraproject.org/koji/taskinfo?taskID=2294313
Comment 6 Paul Flo Williams 2010-08-03 06:32:59 UTC 
I think the fact that this is fixed in your scratch build means that this is fixed in Rawhide and can be closed?
Comment 7 Kevin Fenzi 2010-08-03 15:25:40 UTC 
Sure. ;) 

Normally I would ask the reporter if they needed the newer version in the stable release, but with fontforge, we don't like to upgrade releases as there might be regressions in building fonts. ;(