Description of problem: segmentation fault when using "ftsrting -m $string ppem $fonts_filename". Version-Release number of selected component (if applicable): freetype-2.2.1-21.el5_3 How reproducible: 100% Steps to Reproduce: 1.find the .ttf file in /usr/share/fonts 2.for each .ttf file, run ftsting -m $string ppem $fonts_filename under gnome-terminal. Actual results: come across segmentation fault when using some font files. Expected results: test string display correctly with all types of fonts. Additional info: 1.font files failed in rhel5server--x86_64: /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf # rpm -qf /usr/share/fonts/chinese/TrueType/uming.ttf fonts-chinese-3.02-12.el5.noarc 2.font files failed in rhel5server--ppc: /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf 3.font files failed in rhel5server--ia64: /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf 4.font files failed in rhel5server--i386: /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf 5.font files failed in rhel5client--i386: /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf 6.font files failed in rhel5client--x86_64: /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf 7.font files failed in rhel5client--s390x: /usr/share/fonts/zh_TW/TrueType/bsmi00lp.ttf /usr/share/fonts/chinese/TrueType/ukai.ttf /usr/share/fonts/chinese/TrueType/uming.ttf backtrace file is attached.
Created attachment 344413 [details] bt file
Created attachment 344422 [details] bt file
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
Can you confirm that this only happens with ftstring, and that the fonts work fine in real applications?
I believe this bug doesn't affect any of our applications. I'm inclined to either WONTFIX it or postpone it. Bug exists in upstream also.
If no-one else disagree, I think we should close as WONTFIX and do further testing in Fedora.
Close it as WONTFIX.