$ xemacs
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*,
-*-*-*-*-*-*-*-120-*-iso10646-1,
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0,
-*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that  may describe
your crash, and with luck a workaround.  Please check it first, but do report
the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu.  If necessary, send
ordinary email to `crashes@xemacs.org'.  *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem.  Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type

  gdb /usr/bin/xemacs core

then type `where' at the debugger prompt.  No GDB on your system?  You may
have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

  # bind (frame-being-created)
  make-frame(nil #<x-device on ":0.0" 0xb05>)
  frame-initialize()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (condition-case ... . ((t (byte-code "      \uffff\uffff" ... 1))))
  # bind (error-data)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault


This also happens with xemacs21-mule.
xemacs21-gnome-mule-canna-wnn is fine.

When I set LANG=C, xemacs starts up properly.

ii  mule-ucs       0.84.999+0.200 universal encoding system for Mule

  Hi.

From: Ryan Lovett <ryan@stat.Berkeley.EDU>
Subject: Bug#303103: xemacs21-bin: segfault when LANG=en_US.UTF-8
Date: Mon, 04 Apr 2005 12:16:07 -0700

  There is no problem in my box, even when I set
LANG=en_US.UTF-8.  I think that this is a font setting problem in
your system.  Please check the following things.

1. Check your ~/.Xresources file.
2. In the case that you want to use jisx encoding, do you install
Japanese font?
3. When running xemacs with -q option, do you have the same
problem?

  xemacs21-gnome-* binaries don't use X Font system.

  Thanks for your report.

----
  OHURA Makoto: ohura@debian.org(Debian Project)
                ohura@netfort.gr.jp(LILO/Netfort)
  GnuPG public key: http://www.netfort.gr.jp/~ohura/gpg.asc.txt
                    1024D/77DCE083
        fingerprint: 54F6 D1B1 2EE1 81CD 65E3  A1D3 EEA2 EFA2 77DC E083
http://www.netfort.gr.jp/~ohura/

I unset all properties just to make sure and this still happens.

I actually do not want to use jisx encoding.

Yes, the same thing happens.

Do you know why xemacs is requesting jisx encodings?

Ryan

  Hi.

From: Ryan Lovett <ryan@stat.Berkeley.EDU>
Subject: Bug#303103: xemacs21-bin: segfault when LANG=en_US.UTF-8
Date: Wed, 13 Apr 2005 10:09:01 -0700

  Try the following things;

1. For disabling mule-ucs, set DEB_MULEUCS_UNICODE to `off'.  See
/usr/share/doc/mule-ucs/README.Debian
2. Run xemacs with -q and -no-site-file.

  And,

3. What xfonts do you install?  Send me the output of the
following command;

$ dpkg -l | grep xfonts

  Do you install xfonts-base?

  Thanks.

----
  OHURA Makoto: ohura@debian.org(Debian Project)
                ohura@netfort.gr.jp(LILO/Netfort)
  GnuPG public key: http://www.netfort.gr.jp/~ohura/gpg.asc.txt
        fingerprint: 54F6 D1B1 2EE1 81CD 65E3  A1D3 EEA2 EFA2 77DC E083
http://www.netfort.gr.jp/~ohura/

$ DEB_MULEUCS_UNICODE=off /usr/bin/xemacs -q -no-site-file
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*,
                        -*-*-*-*-*-*-*-120-*-iso10646-1,                       -*-*-*-*-*-*-*-120-*-jisx0208.1983-0,                    -*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that  may describe
your crash, and with luck a workaround.  Please check it first, but do report
the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu.  If necessary, send
ordinary email to `crashes@xemacs.org'.  *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem.  Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type

  gdb /usr/bin/xemacs core

then type `where' at the debugger prompt.  No GDB on your system?  You may
have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

  # bind (frame-being-created)
  make-frame(nil #<x-device on ":0.0" 0xb01>)
  frame-initialize()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (condition-case ... . ((t (byte-code "      \uffff\uffff" ... 1))))
  # bind (error-data)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault

ii  xfonts-100dpi  4.3.0.dfsg.1-1 100 dpi fonts for X
ii  xfonts-75dpi   4.3.0.dfsg.1-1 75 dpi fonts for X
ii  xfonts-base    4.3.0.dfsg.1-1 standard fonts for X
ii  xfonts-base-tr 4.3.0.dfsg.1-1 standard fonts for X (transcoded from ISO 10
ii  xfonts-cmex-bi 0.1-5          Big5+ Chinese Mingti bitmap font (by CMEX &
ii  xfonts-intl-ar 1.2.1-3        International fonts for X -- Arabic
ii  xfonts-intl-as 1.2.1-3        International fonts for X -- Asian
ii  xfonts-intl-ch 1.2.1-3        International fonts for X -- Chinese
ii  xfonts-intl-ch 1.2.1-3        International fonts for X -- Chinese big
ii  xfonts-intl-eu 1.2.1-3        International fonts for X -- European
ii  xfonts-intl-ja 1.2.1-3        International fonts for X -- Japanese
ii  xfonts-intl-ja 1.2.1-3        International fonts for X -- Japanese big
ii  xfonts-scalabl 4.3.0.dfsg.1-1 scalable fonts for X
ii  xfonts-x3270-m 3.3.2p1-1      Font files for the x3270(1) IBM 3270 emulato

(the full package names...)
$ dpkg --get-selections | grep xfonts
xfonts-100dpi                                   install
xfonts-75dpi                                    install
xfonts-base                                     install
xfonts-base-transcoded                          install
xfonts-cmex-big5p                               install
xfonts-intl-arabic                              install
xfonts-intl-asian                               install
xfonts-intl-chinese                             install
xfonts-intl-chinese-big                         install
xfonts-intl-european                            install
xfonts-intl-japanese                            install
xfonts-intl-japanese-big                        install
xfonts-scalable                                 install
xfonts-x3270-misc                               install

Yup. :)

The reason why all the above font packages are installed is that we have a
large and diverse user community so even though I don't use them all, some
users may want to use some of them.

Thanks for your time,
Ryan

Hi!

I had the same problem with xemacs version 21.4.19-2 (and with some
earlier version).  The problem seems to be discovered:

        $ cd xemacs-21.4.19  # go to xemacs sources
        $ rgrep iso10646 .   # I guess the problem concerns UTF8 locale
        only
        ./etc/sample.Xdefaults:
        -*-*-*-*-*-*-*-120-*-iso10646-1, \
        ./etc/sample.Xdefaults:
        -*-*-*-*-*-*-*-120-*-iso10646-1, \
        ./etc/Emacs.ad:                 -*-*-*-*-*-*-*-120-*-iso10646-1,
        \
        ./etc/Emacs.ad:                 -*-*-*-*-*-*-*-120-*-iso10646-1,
        \

Note that font "-*-*-*-*-*-*-*-120-*-iso10646-1" is invalid, I guess the
author meant something like
"-*-*-*-*-*-*-*-120-*-*-*-*-iso10646-1" (several asterisks lost).

So the workaround (except patching and recompiling) is to redefine
incorrectly defined by default 'Emacs*menubar*FontSet' and
'Emacs*popup*FontSet'.  I wrote in ~/.Xresources

        Emacs*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-*-*
          Emacs*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-*-*

and xemacs does not crash any more.

Dear submitter,

as the package xemacs21 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/725883

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)