abrt version: 1.1.14
Attached file: backtrace
cmdline: fontforge theano
reason: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
Open any font with fontforge.
Open a glyph, select all nodes with ctrl+a and press any of the arrow keys.
fontforge crashes and it shouldn't.
Created attachment 465027 [details]
I'll run this by upstream. Thanks for the bug report.
Kevin, it seems that a new version has been released today.
I wonder whether this fixes the issue.
Just in case it helps.
Sure, worth trying. You still on f14?
Can you try this build:
and see if it fixes the issue?
I'm afraid it wasn't fixed yet.
Thanks for the build.
I can't reproduce this crash with the instructions given, so it looks like it isn't just any font and any glyph.
First of all, could you please try it with the simple font I attached to bug 631172:
If this crashes for you, please let me know which glyph you picked and which arrow key you pressed.
If this doesn't crash for you, please let me know if you can reproduce this problem with any of the fonts that are already packaged for Fedora.
(In reply to comment #6)
> I can't reproduce this crash with the instructions given, so it looks like it
> isn't just any font and any glyph.
> First of all, could you please try it with the simple font I attached to bug
It crashes: exclamation mark and right.
OK, thanks for the update.
I'm using fontforge-20100501-7.fc14.x86-64 (still in updates-testing). I see you're on i686, and I'm hoping that's not the crucial difference.
I open Domino.sfd from the attachment, double click on exclamation mark, Ctrl+A to select all points and press right arrow.
I see all points of the glyph move right. Any other direction is fine too.
My next move will be to update my laptop to F14 i686 and try to reproduce there.
(In reply to comment #4)
> Sure, worth trying. You still on f14?
> Can you try this build:
> and see if it fixes the issue?
Here is the reply that George Williams gave to my bug report (on the fontforge-devel mailing list): http://sourceforge.net/mailarchive/message.php?msg_id=27113987.
It seems that there might be something wrong with the source version.
Thanks for your help,
Created attachment 481162 [details]
backtrace from new build
I've now tracked this down to an error that still exists in current upstream, so I've supplied a patch.
Now waiting on confirmation upstream before applying the patch here.
Pablo, can you try this build
and see if it fixes the issue? It works for me.
(In reply to comment #12)
> Pablo, can you try this build
> and see if it fixes the issue? It works for me.
It works for me too.
Many thanks for your help,
fontforge-20100501-8.fc14 has been submitted as an update for Fedora 14.
fontforge-20100501-8.fc15 has been submitted as an update for Fedora 15.
Wouldn't it be better to patch the latest version and include this in Fedora 15?
Well, for 15 it's possible, but in general we don't like to update fontforge in stable releases. It's used to build many fonts, and if there was a regression it would cause lots of problems for fonts updates.
We can see if fonts folks are ok with updating 15 though, since it's not yet released.
There is still time to update 15 but someone needs to organize a mass rebuild to make sure the new version works with existing fonts (and notify package maintainers so they don't get offended someone else touches their package)
fontforge-20110222-3.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fontforge-20110222-3.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fontforge-20100501-8.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
fontforge-20110222-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.