Description of problem: After Fontforge is opened, a menu is displayed that prompts you to choose a font to edit or create a new font. After selecting one of these, the program crashes. When run from the command line, the following text is shown: Copyright (c) 2000-2009 by George Williams. Executable based on sources from 14:20 GMT 24-Feb-2009. Library based on sources from 14:18 GMT 24-Feb-2009. Failed to create a fontset for the input method -urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-1,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-2,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-3,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-4,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-5,-misc-ar pl ukai tw-medium-r-normal--16-0-0-0-c-0-iso8859-7,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-9,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-10,-misc-ar pl uming tw-light-r-normal--16-0-0-0-c-0-iso8859-13,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso8859-15,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-koi8-uni,-urw-urw gothic l-medium-r-normal--16-0-0-0-p-0-iso10646-1 Help! Server claimed font -misc-ar pl ukai tw-medium-r-normal--13-0-0-0-c-0-iso10646-1 existed in the font list, but when I asked for it there was nothing. I may crash soon. Segmentation fault Is there any way to fix this? Version-Release number of selected component (if applicable): I have tried both the most recent version from the Fontforge website (http://fontforge.sourceforge.net), fontforge-20090408 and the version in the repositories, fontforge-20090224. How reproducible: It happens every time, no matter what choice you make at the prompt. Steps to Reproduce: 1. Type "fontforge" into the command line 2. 3. Actual results: Fontforge encountered a "Segmentation error." Expected results: Fontforge should have opened a font or created a new one. Additional info:
This looks like a duplicate/variant of bug 466404. Can you try the workaround there to recreate font caches and see if it works? Lets continue debugging this over on that bug. *** This bug has been marked as a duplicate of bug 466404 ***