Red Hat Bugzilla – Bug 470674
xmessage can't find font in Unicode, and then segfaulted
Last modified: 2008-11-12 04:52:18 EST
Created attachment 322962 [details] Example core dump on locale en_US.utf8 Description of problem: $ export LANG=en_US.utf8 [pasha@x-www ~]$ xmessage Test Warning: Unable to load any usable ISO8859 font Segmentation fault (core dump attached) On locale ru_RU.utf8 the same behavior, except of language of message about segmentation fault. On C locale it is only produces warnings, but works: $ export LANG=C [pasha@x-www amurforum_test2]$ xmessage Test Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Version-Release number of selected component (if applicable): $ rpm -qf `which xmessage ` xorg-x11-apps-7.3-3.fc9.i386 $ rpm -qa '*ISO8859*' xorg-x11-fonts-ISO8859-1-75dpi-7.2-6.fc9.noarch
Created attachment 322976 [details] script to generate backtrace I am sorry, but it is actually by far the most simple to generate useful backtrace on your computer. Could you please make sure that you have installed yum-utils and gdb packages, and the download -debuginfo packages running debuginfo-install xorg-x11-apps.$(uname -i) Then run the attached script gbt like this gbt xmessage core.1055 Script should generate file xmessage-backtrace-1055.txt. Could you please attach this file to this bug as uncompressed attachment? Thank you
Please excuse me for long reply at this time I have huge amount of work... I'm install all debuginfo packages and ... and can't reproduce error anymore! I even do not rebuild computer (but have xorg restarted once) So, I can't even suppose what was a key to the problem. There exactly same versions of component. # rpm -qf `which xmessage ` xorg-x11-apps-7.3-3.fc9.i386 # rpm -qa '*ISO8859*' xorg-x11-fonts-ISO8859-1-75dpi-7.2-6.fc9.noarch I'm update other software, and possibility problem has been fixed in related libraries... So, I'm try to find problem and reproduce error again, but without success. If I can do it, I will wrote there immediately.
Thanks a lot, Pavel, for reporting the bug and taking all the effort to get us the information. If you ever hit this again, please, feel free to reopen this with the relevant info. Until then, I am closing this as WORKSFORME.