From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
When I run ami, nothing appears to happen although something appears in the
Gnome taskbar - the application didn't pop-up. It is one of those rectangle
things with 2x2 hexadecimal numbers in them indicating that some charset or font
isn't working properly.
The actual application itself seems devoid of text, with several blank tabs. I
can see radial button widgets, textboxs and a checkbox, but no text labels.
Version-Release number of selected component (if applicable):
Tested on two systems, one with Korean language support installed, one without.
Steps to Reproduce:
1. Run "ami"
Can you please post your /etc/sysconfig/i18n file please?
Also can you check whether ttfonts-ko file is installed?
It says the following when I run it from a console:
[root@laptop root]# ami
** WARNING **: fontset(*,*) loading failed
** WARNING **:
** WARNING **: fontset(*,-*-*-medium-r-normal--16-*-*-*-c-*-*) loading failed
System #1 - without Korean chosen as an extra language during install
[root@laptop root]# cat /etc/sysconfig/i18n
ttfonts-ko is not installed
System #2 - with Korean chosen as an extra language during install
[root@ltspserver root]# cat /etc/sysconfig/i18n
ttfonts-ko is installed
It does work when you run it with "LANG=ko_KR ami", but it seems broken that its
display is completely messed up when you run it with LANG=en_US.UTF-8.
AMI is meant to work under LANG=ko_KR.
That is the only way at the moment.
But for the future, we will keep it in mind that it would be great to be able to
use the multiple language IM's on different LANG settings.
Thanks for the input!
Re-openning since this now also affects ko_KR.UTF-8 in rawhide. ;-)
Probably the cleanest and best solution would be to change the locale
inside AMI to be ko_KR.eucKR internally.
An alternative would be to tweak "/etc/X11/xinit/xinitrc.d/xinput"
to run ami in ko_KR, but that wouldn't solve Warren's problem for
example of course.
Jens, i revisited the bug and thought it may related to the ordering of the
fontset. Tested against patches in 101377 and it works fine. Closing the bug
with duplicate of 101377.
*** This bug has been marked as a duplicate of 101377 ***