Description of problem: Editing glyphs in character view of fontforge segfaults if 5 or more spline points have been selected and any keyboard key is pressed. A gdb backtrace of the segfault in the x86_64 version provides no useful information, but the i586 version show the segfault happening in cvundoes.c:552 The CodeView stucture, cv, seems to be corrupted at that point and the index into cv->layerheads is out of bounds. Version-Release number of selected component (if applicable): fontforge-1.0-0.20110222.3.mga2.i586.rpm fontforge-1.0-0.20110222.3.mga2.x86_64.rpm How reproducible: Every time. Steps to Reproduce: 1. Open any vector based font (ttf or type1 for example) in fontforge. 2. Double click on any basic Latin character to open character view. Make sure the glyph you choose is not a reference to another glyph. 3. Either shift-click or click-drag to select 5 or more spline points, then release shift, if necessary. 4. Press any key.
I can reproduce this here (Mageia Linux 2 x86-64). Regards, -- Shlomi Fish
CC: (none) => shlomif
(In reply to comment #1) > I can reproduce this here (Mageia Linux 2 x86-64). > > Regards, > > -- Shlomi Fish OK, it seems to be fixed in the new fontforge package (with version 20120731-b) that I packaged for Mageia Cauldron. Please try to build the .src.rpm locally and let me know if it fixed the problem for you: http://pkgsubmit.mageia.org/ Regards, -- Shlomi Fish
William Murphy, could you please answer to Shlomi Fish so that we know that it was fixed and we can issue an update candidate to fontforge in Mageia 2?
Keywords: (none) => NEEDINFO, PATCH, Triaged, UPSTREAMCC: (none) => stormi
(In reply to Samuel VERSCHELDE from comment #3) > William Murphy, could you please answer to Shlomi Fish so that we know that > it was fixed and we can issue an update candidate to fontforge in Mageia 2? Was just reminded to turn on email in my preferences a few weeks ago. All on now. Sorry about that... :-| > (In reply to comment #1) > OK, it seems to be fixed in the new fontforge package (with version > 20120731-b) that I packaged for Mageia Cauldron. Please try to build the > .src.rpm locally and let me know if it fixed the problem for you: > Regards, > > -- Shlomi Fish Yes, it's been working nicely since then. No more segfaults. Thank you. :)
> > (In reply to comment #1) > > OK, it seems to be fixed in the new fontforge package (with version > > 20120731-b) that I packaged for Mageia Cauldron. Please try to build the > > .src.rpm locally and let me know if it fixed the problem for you: > > > Regards, > > > > -- Shlomi Fish > > Yes, it's been working nicely since then. No more segfaults. Thank you. :) You're welcome. I've rebuilt it for Mageia 2 in core/updates_testing and now QA should check it. See http://pkgsubmit.mageia.org/ . Regards, -- Shlomi Fish
Hi all, I'm assigning this package ( fontforge ) to QA, but did not write the advisory yet because there is no easy way to list the packages and create a template of the advisory. I think there should be such a template in the "uploaded" fold of each package here: http://pkgsubmit.mageia.org/ If you can tell me how to create a list of the right RPMs and SRPMs, please do so. Sorry for being a little spoiled. Regards, -- Shlomi Fish
Status: NEW => ASSIGNEDAssignee: bugsquad => qa-bugs
(In reply to Shlomi Fish from comment #6) > If you can tell me how to create a list of the right RPMs and SRPMs, please > do so. Sorry for being a little spoiled. You can get them from the rpm build logs, or wait for a few hours and produce them from http://mageia.madb.org/tools/updates, "RPMs" link
Keywords: NEEDINFO => (none)
Mageia 2 partial match *** Arch: i586 *** RPMs from 'core-updates_testing' ======================== fontforge-1.0-0.20120731.1.mga2.i586.rpm SRPMs from 'core-updates_testing' ======================== fontforge-1.0-0.20120731.1.mga2.src.rpm *** Arch: x86_64 *** RPMs from 'core-updates_testing' ======================== fontforge-1.0-0.20120731.1.mga2.x86_64.rpm SRPMs from 'core-updates_testing' ======================== fontforge-1.0-0.20120731.1.mga2.src.rpm
Testing complete mga2 32 Before ------ libpng: libpng.so.2: cannot open shared object file: No such file or directory libpng: libpng.so.2: cannot open shared object file: No such file or directory libpng: libpng.so.2: cannot open shared object file: No such file or directory Segmentation fault After ----- libpng: libpng.so.2: cannot open shared object file: No such file or directory libpng: libpng.so.2: cannot open shared object file: No such file or directory libpng: libpng.so.2: cannot open shared object file: No such file or directory No segfault. We don't appear to have libpng.so.2. Is that anything to be concerned about?
Whiteboard: (none) => mga2-64-ok
Whiteboard: mga2-64-ok => mga2-32-ok
Testing complete mga2 64
Whiteboard: mga2-32-ok => mga2-32-ok mga2-64-ok
Validating. Advisory uploaded. Could sysadmin please push from 2 core/updates_testing to updates Thanks!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Update pushed: :http://advisories.mageia.org/MGAA-2013-0106.html
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED