Created attachment 479522 [details] Toy program to test XCreateFontSet. Description of problem: Recently, I found my tcltk app failed to invoke ibus under LANG=ja_JP.UTF-8. With LANG=ja_JP.eucJP, it worked perfectly. After some debugging, I found that XCreateFontSet for "-*-*-*-R-Normal--14-130-75-75-*-*" is not working. It returns empty fontset in UTF-8. (In eucJP, it returns valid fontset). This is caused by lack of 'scaled' version of 75dpi and misc fonts. So please add following symlinks too: /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:pri=5 -> /usr/share/X11/fonts/75dpi /etc/X11/fontpath.d/xorg-x11-fonts-misc:pri=5 -> /usr/share/X11/fonts/misc # Priority is lowered than unscaled version. Version-Release number of selected component (if applicable): xorg-x11-fonts-7.2-9.fc12.src.rpm xorg-x11-fonts-ISO8859-1-75dpi-7.2-9.fc12.noarch xorg-x11-fonts-misc-7.2-9.fc12.noarch How reproducible: Steps to Reproduce: 1. Run "echo 'pack [text .t]' | wish" 2. Type ibus hot key. Actual results: no effect. Expected results: ibus window pops up. Additional info:
If I just scratch built a Rawhide package for F13 (http://koji.fedoraproject.org/koji/taskinfo?taskID=2878536), does it work for you?
(In reply to comment #1) > If I just scratch built a Rawhide package for F13 > (http://koji.fedoraproject.org/koji/taskinfo?taskID=2878536), does it work for > you? Thank you for your response! It may (if it has correct fontpaths). Where can I download its src.rpm now? I will rebuild it, test it and report result.
(In reply to comment #2) > (In reply to comment #1) > > If I just scratch built a Rawhide package for F13 > > (http://koji.fedoraproject.org/koji/taskinfo?taskID=2878536), does it work for > > you? > > Thank you for your response! > > It may (if it has correct fontpaths). > Where can I download its src.rpm now? > I will rebuild it, test it and report result. Damn, stupid Koji, I forgot it doesn't provide them on the webpage for scratch builds. Take a look at http://koji.fedoraproject.org/scratch/mcepl/task_2878536/ there should be everything you need.
(In reply to comment #3) > Damn, stupid Koji, I forgot it doesn't provide them on the webpage for scratch > builds. Take a look at > http://koji.fedoraproject.org/scratch/mcepl/task_2878536/ there should be > everything you need. Thank you! and It worked! I tested your noarch.rpm on two hosts and both can now handle xim correctly. Thank you!
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.