Description of problem: Was in file-select dialog, choosing folders and subfolders, and FontForge suddenly crashed. Version-Release number of selected component: fontforge-20120731b-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/fontforge crash_function: pdf_findobject kernel: 3.7.3-101.fc17.i686.PAE truncated backtrace: :Thread no. 1 (10 frames) : #0 pdf_findobject at parsepdf.c:461 : #2 pdf_findfonts at parsepdf.c:529 : #3 NamesReadPDF at parsepdf.c:2020 : #4 GetFontNames at scripting.c:1634 : #5 WithinList at openfontdlg.c:521 : #6 e_h at openfontdlg.c:556 : #7 _GWidget_Container_eh at gcontainer.c:393 : #8 _GWidget_TopLevel_eh at gcontainer.c:737 : #10 dispatchEvent at gxdraw.c:3869 : #11 GXDrawProcessOneEvent at gxdraw.c:3901
Created attachment 691122 [details] File: core_backtrace
Created attachment 691123 [details] File: environ
Created attachment 691124 [details] File: limits
Created attachment 691125 [details] File: backtrace
Created attachment 691126 [details] File: cgroup
Created attachment 691127 [details] File: smolt_data
Created attachment 691128 [details] File: executable
Created attachment 691129 [details] File: maps
Created attachment 691130 [details] File: dso_list
Created attachment 691131 [details] File: proc_pid_status
Created attachment 691132 [details] File: open_fds
Created attachment 691133 [details] File: var_log_messages
In the Open dialog, you had the filter set to "Extract from PDF", didn't you? Unfortunately, FontForge doesn't support some common compression techniques used in modern PDFs (version 1.5 and above) and, as you have seen, makes a very bad attempt. This is the case even for the very latest upstream code, I'm afraid, so this is unlikely to be fixed any time soon.
Although this has been submitted upstream and no progress has been made, we have a way forward locally, so I'm reopening this. Although correctly processing newer PDFs is a large job, I can stop FontForge crashing by at least recognising the PDFs that will crash. I'll be applying a patch shortly.
*** Bug 949287 has been marked as a duplicate of this bug. ***
fontforge-20120731b-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fontforge-20120731b-7.fc19
fontforge-20120731b-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fontforge-20120731b-5.fc18
fontforge-20120731b-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fontforge-20120731b-5.fc17
Package fontforge-20120731b-7.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fontforge-20120731b-7.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5863/fontforge-20120731b-7.fc19 then log in and leave karma (feedback).
fontforge-20120731b-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
fontforge-20120731b-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
fontforge-20120731b-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.