Commit 624e7dc7 authored by Glenn Morris's avatar Glenn Morris

Update GNOME bugtracker URLs

*, admin/notes/multi-tty, etc/PROBLEMS:
* src/emacs.c (main):
* src/xterm.c (x_connection_closed): Update GNOME bugtracker URLs.
; * src/gtkutil.c (xg_display_close):
; * src/image.c (svg_load_image): Update URLs in comments.
parent 51ef6d55
......@@ -305,7 +305,7 @@ THINGS TO DO
multidisplay (and don't mind core dumps), you can edit src/config.h
and define HAVE_GTK_MULTIDISPLAY there by hand.
Update: Han reports that GTK+ version 2.8.9 almost gets display
disconnects right. GTK will probably be fully fixed by the time
......@@ -2659,7 +2659,7 @@ if test x"$pkg_check_gtk" = xyes; then
closing open displays. This is no problem if you just use
one display, but if you use more than one and close one of them
Emacs may crash.
......@@ -207,7 +207,7 @@ configuring your compiler to use the native linker instead of GNU ld.
** When Emacs is compiled with Gtk+, closing a display kills Emacs.
There is a long-standing bug in GTK that prevents it from recovering
from disconnects:
from disconnects:
Thus, for instance, when Emacs is run as a server on a text terminal,
and an X frame is created, and the X server for that frame crashes or
......@@ -225,7 +225,7 @@ The error message is:
X protocol error: BadMatch (invalid parameter attributes) on protocol request 140
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug:
This is a GTK bug:
For details, see etc/PROBLEMS.
Fatal error 6: Aborted
......@@ -1164,7 +1164,7 @@ is running. If gnome-settings-daemon is not running, Emacs receives
input through XIM without any problem. Furthermore, this seems only
to happen in *.UTF-8 locales; zh_CN.GB2312 and zh_CN.GBK locales, for
example, work fine. A bug report has been filed in the Gnome
*** Gnome: GPaste clipboard manager causes erratic behavior of 'yank'
......@@ -1067,7 +1067,7 @@ main (int argc, char **argv)
#endif /* HAVE_LIBSYSTEMD */
#ifdef USE_GTK
fprintf (stderr, "\nWarning: due to a long standing Gtk+ bug\n\n\
fprintf (stderr, "\nWarning: due to a long standing Gtk+ bug\n\n\
Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.\n\
Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.\n");
#endif /* USE_GTK */
......@@ -259,7 +259,7 @@ xg_display_close (Display *dpy)
#if GTK_CHECK_VERSION (2, 0, 0) && ! GTK_CHECK_VERSION (2, 10, 0)
/* GTK 2.2-2.8 has a bug that makes gdk_display_close crash (bug This way we This way we
can continue running, but there will be memory leaks. */
g_object_run_dispose (G_OBJECT (gdpy));
......@@ -9302,7 +9302,7 @@ svg_load_image (struct frame *f, struct image *img, char *contents,
/* Set base_uri for properly handling referenced images (via 'href').
See rsvg bug 596114 - "image refs are relative to curdir, not .svg file"
( */
( */
if (filename)
rsvg_handle_set_base_uri(rsvg_handle, filename);
......@@ -9812,13 +9812,13 @@ x_connection_closed (Display *dpy, const char *error_message, bool ioerror)
current Xt versions, this isn't needed either. */
#ifdef USE_GTK
/* A long-standing GTK bug prevents proper disconnect handling
( Once,
( Once,
the resulting Glib error message loop filled a user's disk.
To avoid this, kill Emacs unconditionally on disconnect. */
shut_down_emacs (0, Qnil);
fprintf (stderr, "%s\n\
When compiled with GTK, Emacs cannot recover from X disconnects.\n\
This is a GTK bug:\n\
This is a GTK bug:\n\
For details, see etc/PROBLEMS.\n",
emacs_abort ();
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment