Bug 1429574

Summary: [abrt] fontforge: PyFF_OpenFont(): fontforge killed by signal 6
Product: [Fedora] Fedora Reporter: Parag Nemade <pnemade>
Component: fontforgeAssignee: Parag Nemade <pnemade>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: kevin, paul, pnemade
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9871cf6d409b7130a02ad1c7a865c8157eb5d2d6
Whiteboard: abrt_hash:98f7901993fb51c3287036f9412eddabb3acf6b7;VARIANT_ID=workstation;
Fixed In Version: fontforge-20161012-6.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-01 16:54:26 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: FreeSans.sfd
none
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: generate.ff
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Parag Nemade 2017-03-06 16:03:47 UTC
Description of problem:
1) Use a simple fontfore script where it will open the sfd file e.g. say generate.ff
fontforge.open()
2) get any sfd file e.g. FreeSans.sfd from gnu-free-fonts upstream tarball

3) run following command
/usr/bin/fontfore -lang=py -script generate.ff FreeSans.sfd

This will cause core dump.

Version-Release number of selected component:
fontforge-20161012-5.fc26

Additional info:
reporter:       libreport-2.9.0
backtrace_rating: 4
cmdline:        /usr/bin/fontforge -lang=py -script generate.ff FreeSans.sfd
crash_function: PyFF_OpenFont
executable:     /usr/bin/fontforge
journald_cursor: s=c46a08e401524c2d8475cc7b17d07a17;i=35b2;b=b1f802c909064194963cc056c3ca447a;m=85a180071;t=54a10b828e9da;x=38d0814c5125f170
kernel:         4.11.0-0.rc0.git6.1.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #6 PyFF_OpenFont at python.c:1013
 #7 _PyCFunction_FastCallDict at /usr/src/debug/Python-3.6.0/Objects/methodobject.c:234
 #8 _PyCFunction_FastCallKeywords at /usr/src/debug/Python-3.6.0/Objects/methodobject.c:295
 #9 call_function at /usr/src/debug/Python-3.6.0/Python/ceval.c:4788
 #10 _PyEval_EvalFrameDefault at /usr/src/debug/Python-3.6.0/Python/ceval.c:3275
 #11 _PyEval_EvalCodeWithName at /usr/src/debug/Python-3.6.0/Python/ceval.c:4119
 #12 PyEval_EvalCodeEx at /usr/src/debug/Python-3.6.0/Python/ceval.c:4140

Comment 1 Parag Nemade 2017-03-06 16:20:38 UTC
Finally I managed to report this bug from a F26 VM where I faced some dual mouse pointer issue :)

The attachments are on their way from abrt tool, still attaching.

Comment 2 Parag Nemade 2017-03-06 16:23:05 UTC
Created attachment 1260453 [details]
File: FreeSans.sfd

Comment 3 Parag Nemade 2017-03-06 16:23:11 UTC
Created attachment 1260454 [details]
File: backtrace

Comment 4 Parag Nemade 2017-03-06 16:23:13 UTC
Created attachment 1260455 [details]
File: cgroup

Comment 5 Parag Nemade 2017-03-06 16:23:16 UTC
Created attachment 1260456 [details]
File: core_backtrace

Comment 6 Parag Nemade 2017-03-06 16:23:18 UTC
Created attachment 1260457 [details]
File: dso_list

Comment 7 Parag Nemade 2017-03-06 16:23:21 UTC
Created attachment 1260458 [details]
File: environ

Comment 8 Parag Nemade 2017-03-06 16:23:23 UTC
Created attachment 1260459 [details]
File: generate.ff

Comment 9 Parag Nemade 2017-03-06 16:23:25 UTC
Created attachment 1260460 [details]
File: limits

Comment 10 Parag Nemade 2017-03-06 16:23:31 UTC
Created attachment 1260461 [details]
File: maps

Comment 11 Parag Nemade 2017-03-06 16:23:33 UTC
Created attachment 1260462 [details]
File: open_fds

Comment 12 Parag Nemade 2017-03-06 16:23:35 UTC
Created attachment 1260463 [details]
File: proc_pid_status

Comment 13 Parag Nemade 2017-03-06 16:23:38 UTC
Created attachment 1260464 [details]
File: var_log_messages

Comment 14 Parag Nemade 2017-03-07 11:00:52 UTC
Reported upstream issue -> https://github.com/fontforge/fontforge/issues/3042

Comment 15 Fedora Update System 2017-03-10 01:39:28 UTC
fontforge-20161012-6.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-57809d7ec3

Comment 16 Fedora Update System 2017-03-11 00:21:37 UTC
fontforge-20161012-6.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-57809d7ec3

Comment 17 Fedora Update System 2017-04-01 16:54:26 UTC
fontforge-20161012-6.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.