Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: [abrt] crash in fontforge-20090622-2.fc12: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=572427
Summary: [abrt] crash in fontforge-20090622-2.fc12: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV) Product: Fedora Version: 12 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:76dd7d152233d7934b4bb42e08385d8ac4cb7e3b Severity: medium Priority: low Component: fontforge AssignedTo: kevin@tummy.com ReportedBy: cchance@redhat.com QAContact: extras-qa@fedoraproject.org CC: roozbeh@gmail.com, kevin@tummy.com, fonts-bugs@lists.fedoraproject.org Classification: Fedora Target Release: ---
abrt 1.0.7 detected a crash.
architecture: x86_64 Attached file: backtrace cmdline: fontforge component: fontforge executable: /usr/bin/fontforge kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: fontforge-20090622-2.fc12 rating: 4 reason: Process /usr/bin/fontforge was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
How to reproduce ----- 1. Open a font file by File > Open or on command line. 2. Hint > edit cvt table. 3. Expand the cvt table window. 4. It crashed.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
--- Comment #1 from Caius 'kaio' Chance cchance@redhat.com 2010-03-11 01:54:29 EST --- Created an attachment (id=399264) --> (https://bugzilla.redhat.com/attachment.cgi?id=399264) File: backtrace
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
Kevin Fenzi kevin@tummy.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #2 from Kevin Fenzi kevin@tummy.com 2010-03-11 12:10:44 EST --- This is reproducable anytime via the above info?
I will report this upstream. Unless you would like to do so to the fontforge-devel list?
Thanks for the report!
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
--- Comment #3 from Caius 'kaio' Chance cchance@redhat.com 2010-03-11 19:32:49 EST --- (In reply to comment #2)
This is reproducable anytime via the above info?
I have tried more than 3 times on my machine yesterday. It was at the latest yum'ed state.
I will report this upstream. Unless you would like to do so to the fontforge-devel list?
Please do. :)
Thanks for the report!
Thank you, too.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
Kevin Fenzi kevin@tummy.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(me@kaio.net)
--- Comment #4 from Kevin Fenzi kevin@tummy.com 2010-07-04 15:07:19 EDT --- I don't see this anymore in newer fontforge versions.
Can you confirm that it's fixed for you now?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
Paul Flo Williams paul@frixxon.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |paul@frixxon.co.uk
--- Comment #5 from Paul Flo Williams paul@frixxon.co.uk 2010-07-13 07:34:06 EDT --- See also bug 610168.
From that bug, fontforge-20090923-3.fc13 still has problem, but your latest
scratch build (below), from the 20100501 sources, no longer has this problem.
http://koji.fedoraproject.org/koji/taskinfo?taskID=2294313
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
--- Comment #6 from Paul Flo Williams paul@frixxon.co.uk 2010-08-03 02:32:59 EDT --- I think the fact that this is fixed in your scratch build means that this is fixed in Rawhide and can be closed?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=572427
Kevin Fenzi kevin@tummy.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |RAWHIDE Flag|needinfo?(me@kaio.net) |
--- Comment #7 from Kevin Fenzi kevin@tummy.com 2010-08-03 11:25:40 EDT --- Sure. ;)
Normally I would ask the reporter if they needed the newer version in the stable release, but with fontforge, we don't like to upgrade releases as there might be regressions in building fonts. ;(
fonts-bugs@lists.fedoraproject.org