procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* etc/PROBLEMS: New entry about GTK+ 3 crash with some X servers.

Browse source
This commit is contained in:
Glenn Morris 2018-08-28 16:05:04 -04:00
parent 9d61344499
commit 3764ab4186
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
etc/PROBLEMS
View file

@ -217,6 +217,26 @@ result in an endless loop.
If you need Emacs to be able to recover from closing displays, compile If you need Emacs to be able to recover from closing displays, compile
it with the Lucid toolkit instead of GTK. it with the Lucid toolkit instead of GTK.
** Emacs compiled with GTK+ 3 crashes when run under some X servers.
This happens when the X server does not provide certain display
features that the underlying GTK+ 3 toolkit assumes. For example, this
issue has been seen with remote X servers like X2Go. The symptoms
are an Emacs crash, possibly triggered by the mouse entering the Emacs
window, or an attempt to resize the Emacs window. The crash backtrace
contains a call to XQueryPointer.
This issue was fixed in the GTK+ 3 toolkit in commit 4b1c0256 in February 2018.
If your GTK+ 3 is still affected, you can avoid the issue by recompiling
Emacs with a different X toolkit, eg --with-toolkit=gtk2.
References:
https://gitlab.gnome.org/GNOME/gtk/commit/4b1c02560f0d8097bf5a11932e52fb72f3e9e94b
https://debbugs.gnu.org/24280
https://bugs.debian.org/901038
https://bugzilla.redhat.com/1483942
https://access.redhat.com/solutions/3410101
** Emacs compiled with GTK crashes at startup due to X protocol error. ** Emacs compiled with GTK crashes at startup due to X protocol error.
This is known to happen on elementary OS GNU/Linux systems. This is known to happen on elementary OS GNU/Linux systems.