FS#20430 - [fontforge] crashes on selection contours undo operation [ctrl + a then any key segfaults fontforge]

Attached to Project: Arch Linux
Opened by asif ali rizvan (fast_rizwaan) - Tuesday, 10 August 2010, 18:17 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 14 December 2011, 10:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: select-all (ctrl+a, or mouse double click contour selection) then any keyboard key like ctrl key, or a or i key crashes fontforge in Archlinux


Additional info:
* package version(s)
$ fontforge --version
Copyright (c) 2000-2010 by George Williams.
Executable based on sources from 11:21 GMT 1-May-2010-ML.
Library based on sources from 03:43 GMT 29-Apr-2010.
fontforge 20100501
libfontforge 20100429-ML

20100501
* config and/or log files etc.


Steps to reproduce:

1. open a font say arial.ttf or times.ttf
2. open a 'gylph' window by double clicking on say number 4 character in the font
3. after the gylph window opens,
4. press ctrl+a or double-click on the 'contours' to select all lines.
5. now press any key, say ctrl key.
6. fontforge segfaults.


Expected Behavior:

1. fontforge (0.0.20090923-2)in Kubuntu 10.04 lucid: http://packages.ubuntu.com/lucid/fontforge does not crash, which suggests, that new version got this segfault, somehow got a bug, or ubuntu patches it.. don't know.

select all is a very very basic activity in gylpy, when we copy-paste a gylph, select all is always done on the contours. so, as soon as we press a key to resize, move operations, fontforge would crash.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 14 December 2011, 10:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  fontforge-20111214-1 in [testing]
Comment by Gaetan Bisson (vesath) - Friday, 12 November 2010, 23:44 GMT
I've compiled fontforge-0.0.20090923 with the same patches and configure options as Ubuntu, but the bug is still here.
If you still have the Ubuntu system at hand, could you tell me if http://packages.ubuntu.com/natty/fontforge is exempt of this bug?
Comment by Gaetan Bisson (vesath) - Saturday, 13 November 2010, 13:54 GMT
Even a vanilla CVS version (with only the python-2.7 compatibility patch) features this bug.
Attached is a backtrace, which I'll look at in detail as soon as I have the time.

Anyhow, this sounds like an upstream bug to me: has it been reported there?
   fontforge.bt (2.1 KiB)
Comment by Gaetan Bisson (vesath) - Monday, 15 November 2010, 23:32 GMT
I tried today on an Ubuntu 10.10 and, indeed, it does not feature this bug.

I'm really not sure, however, what is wrong with our fontforge build, or if the problem is in some dependency... I'll keep searching but any help is welcome.
Comment by Gaetan Bisson (vesath) - Wednesday, 05 January 2011, 01:22 GMT
Compiling with -O2 is the cause of this problem (don't ask me why; I only know that compiling with -O1 is a solution to it); expect fontforge-20100501-5 in [extra] soon.
Comment by Kamil Stachowski (caminoix) - Monday, 15 August 2011, 19:15 GMT
The bug is featured again in fontforge-20110222-2.

Loading...