Fresh install of suse 9.2 on a P4 with 512 meg memory. Previously installed GnuEmacs from source. It would not open in a new Xwindow, only in the terminal window. Installaation of GnuEmacs from RPMs failed Installed the following RPMs: canna-libs-3.7p1-27.i586.rpm xemacs-21.4.15-64.3.i586.rpm/ xemacs-info-21.5.18-4.i586.rpm xemacs-packages-20040818-2.1.noarch.rpm xemacs-packages-info-20040202-57.1.i586.rpm not in that order abbysuse:~ # xemacs -i .exrc results in a new xwindow openning briefly and the it goes away. The following eror message is returned: abbysuse:~ # xemacs -i .exrc Loading xlib-xwin... Loading xlib-xwin...doneWarning: Missing charsets in String to FontSet conversion 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(a)xemacs.org&#39;. *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/X11R6/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: # (unwind-protect ...) expand-file-name("init.elc" "~/.xemacs/") # bind (--dolist-temp--15860 file) byte-code("..." [init-directory user-init-file-base-list expanded file --dolist-temp--15860 nil expand-file-name file-readable-p throw found] 4) # (catch found ...) # bind (init-directory init-directory) find-user-init-directory-init-file("~/.xemacs/") # bind (home-directory init-directory) find-user-init-file("~/.xemacs/") load-user-init-file() byte-code("..." [init-file-had-error load-user-init-file-p load-user-init-file nil] 2) # (condition-case ... . ((error (byte-code "Áā�n!\"Ɓǁȁ��n!#��Ï" ... 7)))) # bind (debug-on-error debug-on-error-from-init-file debug-on-error-should-be-set debug-on-error-initial) load-init-file() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " " ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Segmentation fault abbysuse:~ # man ulimit Reformatting bashbuiltins(1), please wait... abbysuse:~ # man ulimit Reformatting ulimit(1p), please wait... abbysuse:~ # xemacs -i .exrc Loading xlib-xwin... Loading xlib-xwin...doneWarning: Missing charsets in String to FontSet conversion 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(a)xemacs.org&#39;. *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/X11R6/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: # (unwind-protect ...) expand-file-name("init.elc" "~/.xemacs/") # bind (--dolist-temp--15860 file) byte-code("..." [init-directory user-init-file-base-list expanded file --dolist-temp--15860 nil expand-file-name file-readable-p throw found] 4) # (catch found ...) # bind (init-directory init-directory) find-user-init-directory-init-file("~/.xemacs/") # bind (home-directory init-directory) find-user-init-file("~/.xemacs/") load-user-init-file() byte-code("..." [init-file-had-error load-user-init-file-p load-user-init-file nil] 2) # (condition-case ... . ((error (byte-code "Áā�n!\"Ɓǁȁ��n!#��Ï" ... 7)))) # bind (debug-on-error debug-on-error-from-init-file debug-on-error-should-be-set debug-on-error-initial) load-init-file() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " " ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Segmentation fault I was unable to find the problem file either on my computer or as a web file. Any suggestions? Thanks Tom