https://bugzilla.redhat.com/show_bug.cgi?id=1471773

            Bug ID: 1471773
           Summary: Opening Fontforge causes its killing by segmentation
                    fault
           Product: Fedora
           Version: 25
         Component: fontforge
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected],
                    [email protected], [email protected]



Description of problem:
When I open Fontforge from terminal, it ends with segfault.

Version-Release number of selected component (if applicable):
fontforge-20160404-5.fc25.x86_64

How reproducible:
Always

Steps to Reproduce:
1. $ fontforge
2. segfault

Actual results:
Segfault

Expected results:
Application is running.

Additional info:
There are messages in terminal during starting up FontForge:

Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 05:58 UTC  8-Mar-2017-ML-D.
 Based on source from git with hash: 
no xdefs_filename!
TESTING: getPixmapDir:/usr/share/fontforge/pixmaps
TESTING: getShareDir:/usr/share/fontforge
TESTING: GResourceProgramDir:/usr/bin
trying default theme:/usr/share/fontforge/pixmaps/resources
fontforge.hasUserInterface!
PyFF_onAppClosing() cnt:1
Segmentation fault (core dumped)

And from journalctl -r:

Jul 17 14:14:52 unused-4-162-brq-redhat-com abrt-hook-ccpp[11022]: Process
11021 (fontforge) of user 28720 killed by SIGSEGV - dumping core
Jul 17 14:14:52 unused-4-162-brq-redhat-com kernel: fontforge[11021]: segfault
at 0 ip 00007fc21dba9790 sp 00007ffc2dbd9f40 error 4 in
libc-2.24.so[7fc21db11000+1bc000]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
fonts-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to