aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggert2018-05-26 16:42:52 -0700
committerPaul Eggert2018-05-26 16:44:09 -0700
commita73e4f53ab86c69fdb8f5869173d6693d73e6fb2 (patch)
tree2845d9e4077a7777fc4b069a21074c95b2b9fe1b
parent6fcab83600317e94ea7b915da7730a8c7e50226d (diff)
downloademacs-a73e4f53ab86c69fdb8f5869173d6693d73e6fb2.tar.gz
emacs-a73e4f53ab86c69fdb8f5869173d6693d73e6fb2.zip
GNOME moved URLs for its active bug reports
* src/emacs.c (main) [USE_GTK]: * src/gtkutil.c (xg_display_close): * src/xterm.c (x_connection_closed): Update GNOME bug report URLs.
-rw-r--r--admin/notes/multi-tty2
-rw-r--r--configure.ac2
-rw-r--r--etc/PROBLEMS4
-rw-r--r--src/emacs.c2
-rw-r--r--src/gtkutil.c4
-rw-r--r--src/image.c2
-rw-r--r--src/xterm.c4
7 files changed, 10 insertions, 10 deletions
diff --git a/admin/notes/multi-tty b/admin/notes/multi-tty
index 9cfe7aacd35..5b34bb598ef 100644
--- a/admin/notes/multi-tty
+++ b/admin/notes/multi-tty
@@ -305,7 +305,7 @@ THINGS TO DO
305 multidisplay (and don't mind core dumps), you can edit src/config.h 305 multidisplay (and don't mind core dumps), you can edit src/config.h
306 and define HAVE_GTK_MULTIDISPLAY there by hand. 306 and define HAVE_GTK_MULTIDISPLAY there by hand.
307 307
308 http://bugzilla.gnome.org/show_bug.cgi?id=85715 308 https://gitlab.gnome.org/GNOME/gtk/issues/221
309 309
310 Update: Han reports that GTK+ version 2.8.9 almost gets display 310 Update: Han reports that GTK+ version 2.8.9 almost gets display
311 disconnects right. GTK will probably be fully fixed by the time 311 disconnects right. GTK will probably be fully fixed by the time
diff --git a/configure.ac b/configure.ac
index a49b7727975..a11abc1b65b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2684,7 +2684,7 @@ if test x"$pkg_check_gtk" = xyes; then
2684 closing open displays. This is no problem if you just use 2684 closing open displays. This is no problem if you just use
2685 one display, but if you use more than one and close one of them 2685 one display, but if you use more than one and close one of them
2686 Emacs may crash. 2686 Emacs may crash.
2687 See https://bugzilla.gnome.org/show_bug.cgi?id=85715]]) 2687 See https://gitlab.gnome.org/GNOME/gtk/issues/221]])
2688 fi 2688 fi
2689 2689
2690fi 2690fi
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index d42539061be..fe48febfb78 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -207,7 +207,7 @@ configuring your compiler to use the native linker instead of GNU ld.
207** When Emacs is compiled with Gtk+, closing a display kills Emacs. 207** When Emacs is compiled with Gtk+, closing a display kills Emacs.
208 208
209There is a long-standing bug in GTK that prevents it from recovering 209There is a long-standing bug in GTK that prevents it from recovering
210from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715. 210from disconnects: https://gitlab.gnome.org/GNOME/gtk/issues/221
211 211
212Thus, for instance, when Emacs is run as a server on a text terminal, 212Thus, for instance, when Emacs is run as a server on a text terminal,
213and an X frame is created, and the X server for that frame crashes or 213and an X frame is created, and the X server for that frame crashes or
@@ -225,7 +225,7 @@ The error message is:
225 225
226 X protocol error: BadMatch (invalid parameter attributes) on protocol request 140 226 X protocol error: BadMatch (invalid parameter attributes) on protocol request 140
227 When compiled with GTK, Emacs cannot recover from X disconnects. 227 When compiled with GTK, Emacs cannot recover from X disconnects.
228 This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 228 This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
229 For details, see etc/PROBLEMS. 229 For details, see etc/PROBLEMS.
230 Fatal error 6: Aborted 230 Fatal error 6: Aborted
231 231
diff --git a/src/emacs.c b/src/emacs.c
index f25e6126642..8633e934e51 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -1070,7 +1070,7 @@ main (int argc, char **argv)
1070#endif /* HAVE_LIBSYSTEMD */ 1070#endif /* HAVE_LIBSYSTEMD */
1071 1071
1072#ifdef USE_GTK 1072#ifdef USE_GTK
1073 fprintf (stderr, "\nWarning: due to a long standing Gtk+ bug\nhttp://bugzilla.gnome.org/show_bug.cgi?id=85715\n\ 1073 fprintf (stderr, "\nWarning: due to a long standing Gtk+ bug\nhttps://gitlab.gnome.org/GNOME/gtk/issues/221\n\
1074Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.\n\ 1074Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.\n\
1075Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.\n"); 1075Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.\n");
1076#endif /* USE_GTK */ 1076#endif /* USE_GTK */
diff --git a/src/gtkutil.c b/src/gtkutil.c
index 3f21288f461..8cc523649d9 100644
--- a/src/gtkutil.c
+++ b/src/gtkutil.c
@@ -258,8 +258,8 @@ xg_display_close (Display *dpy)
258 } 258 }
259 259
260#if GTK_CHECK_VERSION (2, 0, 0) && ! GTK_CHECK_VERSION (2, 10, 0) 260#if GTK_CHECK_VERSION (2, 0, 0) && ! GTK_CHECK_VERSION (2, 10, 0)
261 /* GTK 2.2-2.8 has a bug that makes gdk_display_close crash (bug 261 /* GTK 2.2-2.8 has a bug that makes gdk_display_close crash
262 http://bugzilla.gnome.org/show_bug.cgi?id=85715). This way we 262 <https://gitlab.gnome.org/GNOME/gtk/issues/221>. This way we
263 can continue running, but there will be memory leaks. */ 263 can continue running, but there will be memory leaks. */
264 g_object_run_dispose (G_OBJECT (gdpy)); 264 g_object_run_dispose (G_OBJECT (gdpy));
265#else 265#else
diff --git a/src/image.c b/src/image.c
index 4d5a1bf5e66..992b225d7b7 100644
--- a/src/image.c
+++ b/src/image.c
@@ -9302,7 +9302,7 @@ svg_load_image (struct frame *f, struct image *img, char *contents,
9302 9302
9303 /* Set base_uri for properly handling referenced images (via 'href'). 9303 /* Set base_uri for properly handling referenced images (via 'href').
9304 See rsvg bug 596114 - "image refs are relative to curdir, not .svg file" 9304 See rsvg bug 596114 - "image refs are relative to curdir, not .svg file"
9305 (https://bugzilla.gnome.org/show_bug.cgi?id=596114). */ 9305 <https://gitlab.gnome.org/GNOME/librsvg/issues/33>. */
9306 if (filename) 9306 if (filename)
9307 rsvg_handle_set_base_uri(rsvg_handle, filename); 9307 rsvg_handle_set_base_uri(rsvg_handle, filename);
9308 9308
diff --git a/src/xterm.c b/src/xterm.c
index 3f956d950d8..4bdec7134f4 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -9828,13 +9828,13 @@ x_connection_closed (Display *dpy, const char *error_message, bool ioerror)
9828 current Xt versions, this isn't needed either. */ 9828 current Xt versions, this isn't needed either. */
9829#ifdef USE_GTK 9829#ifdef USE_GTK
9830 /* A long-standing GTK bug prevents proper disconnect handling 9830 /* A long-standing GTK bug prevents proper disconnect handling
9831 (https://bugzilla.gnome.org/show_bug.cgi?id=85715). Once, 9831 <https://gitlab.gnome.org/GNOME/gtk/issues/221>. Once,
9832 the resulting Glib error message loop filled a user's disk. 9832 the resulting Glib error message loop filled a user's disk.
9833 To avoid this, kill Emacs unconditionally on disconnect. */ 9833 To avoid this, kill Emacs unconditionally on disconnect. */
9834 shut_down_emacs (0, Qnil); 9834 shut_down_emacs (0, Qnil);
9835 fprintf (stderr, "%s\n\ 9835 fprintf (stderr, "%s\n\
9836When compiled with GTK, Emacs cannot recover from X disconnects.\n\ 9836When compiled with GTK, Emacs cannot recover from X disconnects.\n\
9837This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715\n\ 9837This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221\n\
9838For details, see etc/PROBLEMS.\n", 9838For details, see etc/PROBLEMS.\n",
9839 error_msg); 9839 error_msg);
9840 emacs_abort (); 9840 emacs_abort ();