Bug 89409 - mkfontscale segfaults while processing Hershey fonts
Summary: mkfontscale segfaults while processing Hershey fonts
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/mkfont* (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-03 12:30 UTC by Petr Gajdos
Modified: 2018-03-26 09:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
patch by Stefan Dirsch (739 bytes, text/plain)
2015-03-03 12:31 UTC, Petr Gajdos
no flags Details
use /FontName when /FamilyName is missing (731 bytes, text/plain)
2015-03-03 12:33 UTC, Petr Gajdos
no flags Details

Description Petr Gajdos 2015-03-03 12:30:08 UTC
More details at

https://bugzilla.suse.com/show_bug.cgi?id=918466
Comment 1 Petr Gajdos 2015-03-03 12:31:40 UTC
Created attachment 113951 [details]
patch by Stefan Dirsch
Comment 2 Petr Gajdos 2015-03-03 12:33:27 UTC
Created attachment 113952 [details]
use /FontName when /FamilyName is missing
Comment 3 Alan Coopersmith 2018-03-24 07:15:31 UTC
Looks like Stefan pushed this fix himself, without closing this bug:
https://cgit.freedesktop.org/xorg/app/mkfontscale/commit/?id=ecb248d8865df376a97a795c2e4f58a3bf64c3f1
Marking as fixed now.
Comment 4 Stefan Dirsch 2018-03-25 11:41:22 UTC
I can't remember having this pushed myself. Somebody else may have done this. Could be that I've sent it to the devel mailing list. Noticed it recently, that the patch went in upstream, but wasn't aware any longer of this upstream bugreport. Thanks for finding it again and closing!
Comment 5 Alan Coopersmith 2018-03-25 18:25:22 UTC
https://lists.x.org/archives/xorg-devel/2016-May/049648.html 8-)
Comment 6 Stefan Dirsch 2018-03-26 09:36:23 UTC
(In reply to Alan Coopersmith from comment #5)
> https://lists.x.org/archives/xorg-devel/2016-May/049648.html 8-)

Ah! Nice! ;-)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.