Bug#656359: [Pkg-fonts-bugs] Bug#656359: [Pkg-fonts-devel] Bug#656359: Segfault when pressing modifier/arrow keys if more than 4 points are selected

2012-01-19 Thread john knightley
Dear Khaled the segmentation fault is somewhat erratic for example moving around the letter g does not crash but moving say a character at uf8000 does - in some cases starting a new font, making it full unicode going to a higher point and simply pressing element is sufficient to crash. Even if so

Bug#656359: [Pkg-fonts-bugs] Bug#656359: [Pkg-fonts-devel] Bug#656359: Bug#656359: Segfault when pressing modifier/arrow keys if more than 4 points are selected

2012-01-19 Thread john knightley
The problem is in the debian package not with fontforge itself - I just removed the debian fontforge and built fontforge from source using fontforge_full-20110222.tar.bz2. The build from source does not have the same problem. The process of making did require pythonui.c which did not register as a

Bug#656359: [Pkg-fonts-devel] Bug#656359: Bug#656359: fontforge: Segfault when pressing modifier/arrow keys if more than 4 points are selected

2012-01-18 Thread john knightley
Williams himself which may make check dependencies a little harder. Of course saying this does not mean that changing the depends list will solve the problem but it is a good place to start. John Knightley On Thu, Jan 19, 2012 at 6:36 AM, Daniel Kahn Gillmor wrote: > On 01/18/2012 01:33 PM, Theppi