XEmacs crash on startup

[sandor kovacs]

Dear Aidan,

thanks for the tip. For some reason I don't have a .Xresources file,
but the problem is solved to some extent. I found out that the font
paths in the xorg.conf file were incorrect and now I can run XEmacs.
Truth be told I still get an error message if I start it from the
command line, but I can't see any problem with the functionality, so I
will live with it.

Thanks again!!

-Sandor

On 11/28/06, Aidan Kehoe <kehoea at parhasard.net> wrote:
>
>  Ar an seachtú lá is fiche de mí na Samhain, scríobh sandor kovacs:
>
>  > I've been trying to solve this on my own, but can't think of anything else.
>  > I also tried searching for this error, but found no solution offered.
>  > I apologize if there is actually a solution I should have found.
>  >
>  > Here is the problem:
>  >
>  > I upgraded from Kubuntu Draper to Edgy and something happened to (X)Emacs fonts.
>  > When I try to launch XEmacs, it exits with the error message attached.
>  > I also attached the gdb output. The core itself is about 10MB, so I am
>  > not sending that, but I can if you think that helps.
>
> It looks like your X server doesn't provide fonts that our X toolkit assumes
> will be there. To work around this, either install the fonts in question, or
> edit the X resources. The former is Kubuntu-specific, so we can't really
> help you there; the latter involves:
>
> 1. Start xfontsel from an XTerm.
>    xfontsel &
>
> 2. Start XEmacs in the same XTerm.
>    xemacs -nw
>
> 3. In the *scratch* buffer of that XEmacs--the buffer that comes up when you
> start normally, type the following:
>
> (Help-find-file (locate-data-file "sample.Xresources"))
>
> and then, with the cursor after the last ), C-x C-e.
>
> That'll give you our sample Xresources file. You'll need to create a file
> ~/.Xresources with all the lines in the sample Xresources file that mention
> font, edit the fonts listed to reflect fonts that appear on your server
> (xfontsel will allow you to do that), and then apply that to the current
> display with:
>
> 4. xrdb < ~/.Xresources
>
> froman XTerm.
>
>  > Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
>  > Warning: Unable to load any usable ISO8859 font
>  > Warning: Unable to load any usable ISO8859 font
>  > Warning: 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 `xemacs-beta at 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" 0xb11>)
>  >   frame-initialize()
>  >   # bind (debugger debug-on-error command-line-args-left)
>
> --
> Santa Maradona, priez pour moi!
>