Description of problem: When the font attached is opened in FontForge and TrueType option is selected in "Generate Fonts" in FontForge, FontForge segfaults. Version-Release number of selected component (if applicable): fontforge-20090224-2.fc11.i586 Kurier-Regular.otf as is shipped in TeX Live 2008 How reproducible: Open the font attached with FontForge, and select "Generate Fonts" in "File". Choose "TrueType" option, and click on "Save". Then FontForge segfaults. Steps to Reproduce: 1. Open the font attached with "fontforge <path_to_the_attached_font>" 2. Click on File 3. Click on Generate Fonts 4. Select TrueType in export type. 5. Click on "Save". Actual results: FontForge segfaults. Expected results: FontForge does not segfault and Kurier-Regular.ttf is generated in the expected location. Additional info: Vide attachment please.
Created attachment 358384 [details] Segfault Message in gdb
Created attachment 358385 [details] the Font that crashed FontForge
Created attachment 358386 [details] "where"-Message in gdb after FontForge segfaults
Since I passed arguments to rpmbuild to build bytecode interpreter and subpixel hinting in freetype (using fedora's src.rpm), it could be related to freetype. However, a cvs version and the 0622 version of FontForge still fails at the same font. The src.rpm is for freetype-2.3.9-5.fc11.i586 .
Just forgot something --- I built with the cvs FontForge with bytecode interpreter support and the 0622 version without bci.
ok. I will see about reporting this upstream... Thanks for the bug report.
Just an update here. I posted to the upstream devel list and it seems this bug is hopefully fixed in cvs: "I think this one really depends on converting OpenType advanced typographic features to Apple ones. At least that's where the crash occurs. This is now fixed in cvs." So, as soon as there is another release I can whip up a package for you to test with, or if you are brave and willing to build from cvs to confirm it's fixed that would be great too.
Thanks, Kevin, for the package, but I just tested the cvs version with "Version: 01:15 GMT 3-Sep-2009(20090903)" and "Library Version: 02:27 GMT 1-Sep-2009" and the TrueType font is generated successfully. So it is confirmed that the issue is fixed in cvs. (So this bug will be closed?)
Up to you. We can close it out now, or wait until the next release and I will close it when that release lands in Fedora. Which would you prefer?
Since it is fixed already and people encountering similar problem will probably checking out later releases or cvs builds of fontforge, given that the information is still accessible to them, I would prefer to close it so that we get «less» bugs in total. So I will close it now.