[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

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 somewhat difficult to describe there is indeed a serious problem here. I have one machine running ubuntu 9.10 which I have been doing all my fontforge work on because when I update to ubuntu 10.4 I noticed this bug, which has remained though I have updated to 10.10 .

Over the past week I have been preparing to do a fontforge training session in Feb and I myself thought that install rather than updating to Maverick solved the problem because I only tested 'g' .


On Thu, Jan 19, 2012 at 3:21 PM, Khaled Hosny <khaledhosny@eglug.org> wrote:
On Thu, Jan 19, 2012 at 01:35:26AM -0500, Daniel Kahn Gillmor wrote:
> Hi fontforge folks--
> over on Debian, we've just gotten http://bugs.debian.org/656359, which
> appears to contain a reproducible segfault.
> Some folks have suggested that it may be due to more recent versions of
> dependent libraries, but i haven't been able to track it down in more
> detail, i'm afraid.
> From Theppitak's original report, a recipe to produce the crash:
> Steps to reproduce:
> - Start fontforge and create a new font.
> - Randomly choose a first glyph to edit.
> - Draw splines with at least 5 points.
> - Select up to 4 points and press a modifier or arrow key. It won't crash.
> - Select at least 5 points and press a modifier or arrow key. It will
>   always crash.
> Any suggestions?

I can't reproduce this with fontforge built from git master running
under Ubuntu 10.04.


Version: GnuPG v1.4.10 (GNU/Linux)


Pkg-fonts-bugs mailing list

Reply to: