[Bug 720354] [abrt] fontforge-20100501-8.fc14: myerrorhandler: Process /usr/bin/fontforge was killed by signal 6 (SIGABRT)

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 14 18:10:39 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


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

Paul Flo Williams <paul at frixxon.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |needinfo?(bernardobarros at gm
                   |                            |ail.com)

--- Comment #4 from Paul Flo Williams <paul at frixxon.co.uk> 2011-07-14 14:10:39 EDT ---
I can't reproduce this with the same version of FontForge on F14, x86-64 with
GNOME.

The backtrace is very short indeed, and suggests that FontForge didn't last
very long before aborting, because FontForge deliberately aborts when it
encounters a problem with the window manager itself.

1. Which DE are you using? GNOME, KDE, or something else?

2. How quickly did FontForge crash. Was it before showing you the main window?

3. Am I testing with the correct font, the one I mentioned in comment #3?

And then I'd echo Kevin's question:

4. Does this happen every time with that font, and with other fonts?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the fonts-bugs mailing list