[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fehlermeldung bei xemacs21



Hallo Liste,
ich habe xemacs21 unter woody und KDE3.1.2 installiert. Bei Aufruf unter root 
erhalte ich folgende Meldung:

---schnipp---
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified


Initialization error: X server not responding
: ":0.0"
---schnipp---

als normaler User:


---schnipp---
Warning: Cannot convert string "-*-*-medium-r-normal--14-*-*-*-c-*-iso8859-15" 
to type FontStruct
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.

If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes@xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.

If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type

  gdb /usr/bin/xemacs21 core

then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB.  A similar procedure should work for all of
these.  Ask your system administrator if you need more help.)

Lisp backtrace follows:

  # bind (frame-being-created)
  make-frame(nil #<x-device on ":0.0" 0x25b5>)
  frame-initialize()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (unwind-protect ...)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Speicherzugriffsfehler
---schnipp---

Weiß jemand Rat?

Andreas Sonnabend



Reply to: