From 624e7dc77865e0a9359dd7f7b0e861743d091313 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Fri, 24 Aug 2018 13:13:08 -0400 Subject: Update GNOME bugtracker URLs * configure.ac, 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. --- admin/notes/multi-tty | 2 +- configure.ac | 2 +- etc/PROBLEMS | 6 +++--- src/emacs.c | 2 +- src/gtkutil.c | 2 +- src/image.c | 2 +- src/xterm.c | 4 ++-- 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 multidisplay (and don't mind core dumps), you can edit src/config.h and define HAVE_GTK_MULTIDISPLAY there by hand. - http://bugzilla.gnome.org/show_bug.cgi?id=85715 + https://gitlab.gnome.org/GNOME/gtk/issues/221 Update: Han reports that GTK+ version 2.8.9 almost gets display disconnects right. GTK will probably be fully fixed by the time diff --git a/configure.ac b/configure.ac index 9542d441d74..3d39cd0c3ba 100644 --- a/configure.ac +++ b/configure.ac @@ -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. - See https://bugzilla.gnome.org/show_bug.cgi?id=85715]]) + See https://gitlab.gnome.org/GNOME/gtk/issues/221]]) fi fi diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 1e103e9af08..9507a5d9758 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -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: http://bugzilla.gnome.org/show_bug.cgi?id=85715. +from disconnects: https://gitlab.gnome.org/GNOME/gtk/issues/221. 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: https://bugzilla.gnome.org/show_bug.cgi?id=85715 + This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221 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 -bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032 +bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=357032 *** Gnome: GPaste clipboard manager causes erratic behavior of 'yank' diff --git a/src/emacs.c b/src/emacs.c index f5e47428ef9..483e848f6db 100644 --- a/src/emacs.c +++ b/src/emacs.c @@ -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\nhttp://bugzilla.gnome.org/show_bug.cgi?id=85715\n\ + fprintf (stderr, "\nWarning: due to a long standing Gtk+ bug\nhttps://gitlab.gnome.org/GNOME/gtk/issues/221\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 */ diff --git a/src/gtkutil.c b/src/gtkutil.c index 83b306a730a..6b72671da91 100644 --- a/src/gtkutil.c +++ b/src/gtkutil.c @@ -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 - http://bugzilla.gnome.org/show_bug.cgi?id=85715). This way we + https://gitlab.gnome.org/GNOME/gtk/issues/221). This way we can continue running, but there will be memory leaks. */ g_object_run_dispose (G_OBJECT (gdpy)); #else diff --git a/src/image.c b/src/image.c index 4d5a1bf5e66..767979e63bd 100644 --- a/src/image.c +++ b/src/image.c @@ -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" - (https://bugzilla.gnome.org/show_bug.cgi?id=596114). */ + (https://gitlab.gnome.org/GNOME/librsvg/issues/33). */ if (filename) rsvg_handle_set_base_uri(rsvg_handle, filename); diff --git a/src/xterm.c b/src/xterm.c index a5646910334..b2d1b5c1980 100644 --- a/src/xterm.c +++ b/src/xterm.c @@ -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 - (https://bugzilla.gnome.org/show_bug.cgi?id=85715). Once, + (https://gitlab.gnome.org/GNOME/gtk/issues/221). 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: https://bugzilla.gnome.org/show_bug.cgi?id=85715\n\ +This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221\n\ For details, see etc/PROBLEMS.\n", error_msg); emacs_abort (); -- cgit v1.2.1