Added some text about Gtk+ looping when X server dies.
This commit is contained in:
parent
bfd203253d
commit
c4c122cb57
1 changed files with 8 additions and 0 deletions
|
@ -233,6 +233,14 @@ configuring your compiler to use the native linker instead of GNU ld.
|
|||
This happens because of bugs in Gtk+. Gtk+ 2.10 seems to be OK. See bug
|
||||
http://bugzilla.gnome.org/show_bug.cgi?id=85715.
|
||||
|
||||
** Emacs compiled with Gtk+ may loop forever if a display crashes.
|
||||
|
||||
This is related to the bug above. A scenario for this is when emacs is run
|
||||
as a server, and an X frame is created. If the X server for the frame
|
||||
crashes or exits unexpectedly and an attempt is made to create a new
|
||||
frame on another X display, then a Gtk+ error happens in the emacs
|
||||
server that results in an endless loop.
|
||||
|
||||
** Emacs compiled with Gtk+ crashes on startup on Cygwin.
|
||||
|
||||
A typical error message is
|
||||
|
|
Loading…
Add table
Reference in a new issue