summaryrefslogtreecommitdiff
path: root/etc
diff options
context:
space:
mode:
authorJan Djärv <jan.h.d@swipnet.se>2008-12-18 19:18:12 +0000
committerJan Djärv <jan.h.d@swipnet.se>2008-12-18 19:18:12 +0000
commitc4c122cb57baf1586c8760845e9d6d620815080e (patch)
tree41c6db1731cacd597dc6c7409c2e701ba00adb5e /etc
parentbfd203253dc34fe3c77d2155ee6b11b0c8147f8d (diff)
downloademacs-c4c122cb57baf1586c8760845e9d6d620815080e.tar.gz
Added some text about Gtk+ looping when X server dies.
Diffstat (limited to 'etc')
-rw-r--r--etc/PROBLEMS8
1 files changed, 8 insertions, 0 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index cae4f3b956c..9d0b1e74109 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -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