Hmmm.... Now I see what has happened. In short, the bug of xemacs21-mule is fragility of handling buggy/broken font situation.
As I checked and confirmed that /usr/bin/mkcfm is missing on my system. This is a program to generate font metrics file for adobe CID fonts (Asian PS fonts http://en.wikipedia.org/wiki/CID_fonts ). So noise over mkcfm with x-ttcidfont -conf was caused by this missing mkcfm. Then I found that debian changelog "xorg (7.0.0-0ubuntu1) dapper; urgency=low which removed mkcfm. Also upstrean dropped it. https://bugs.freedesktop.org/show_bug.cgi?id=5553 So CID font is not supported under current X and Type 1 font is not used. Since I may have had some old CID fonts before and may have been removed them. Then, due to missing mkcfm, the generated font metrics file etc was out of sync with the current reality. That was buggy font situation. Now that I am CID font free, I am safe. This is quite consistent with how the previous bug reports ended. For msttcorefonts reinstall fixed situation etc. Most reports seem to be fixed when font is reinstalled etc. This also explains why bug was not reproducible. My guess from FDT 5553 bug discussion is that the avoiding of Type1 fonts (Including CID ones) altogether in the xemacs may fix this situation. According to this discussion, error handling of this font is "abort" and that may be the cause of segfault. Anyway, I have usable xemacs21-mule now. (emacs21-mule under X still has funny boxes. That seems different problem.) Osamu -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++ Osamu Aoki <[EMAIL PROTECTED]> Yokohama Japan, GPG-key: A8061F32 .''`. Debian Reference: post-installation user's guide for non-developers : :' : http://qref.sf.net and http://people.debian.org/~osamu `. `' "Our Priorities are Our Users and Free Software" --- Social Contract -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
