Description of problem: Emacs froze after entering a couple of lines of text. Killed the window with xkill, and got the following on the console I started it from. Not sure if the log has anything to do with the freeze, though. I did not background emacs until after it froze. $ xkill Select the window whose client you wish to kill with button 1.... xkill: killing creator of resource 0x2e00143 Connection lost to X server ':0' When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221 For details, see etc/PROBLEMS. (emacs:30568): GLib-WARNING **: 18:55:16.548: g_main_context_prepare() called recursively from within a source's check() or prepare() member. (emacs:30568): GLib-WARNING **: 18:55:16.548: g_main_context_check() called recursively from within a source's check() or prepare() member. [mjs@falcon 2019-08]$ Backtrace: emacs[0x51a392] emacs[0x4ffbf1] emacs[0x51a449] emacs[0x4cb973] emacs[0x4cba8c] /lib64/libX11.so.6(_XIOError+0x52)[0x7fd0a3f024a2] /lib64/libX11.so.6(_XEventsQueued+0x85)[0x7fd0a3effca5] /lib64/libX11.so.6(XPending+0x57)[0x7fd0a3ef1727] /lib64/libgdk-3.so.0(+0x6ed3f)[0x7fd0a45d2d3f] /lib64/libglib-2.0.so.0(g_main_context_prepare+0x1ca)[0x7fd0a407d86a] /lib64/libglib-2.0.so.0(+0x5020b)[0x7fd0a407e20b] /lib64/libglib-2.0.so.0(g_main_context_pending+0x2c)[0x7fd0a407e3ac] /lib64/libgtk-3.so.0(gtk_events_pending+0x12)[0x7fd0a48b4232] emacs[0x4cc39d] emacs[0x506f82] emacs[0x507575] emacs[0x5788ce] emacs[0x5b7ef4] emacs[0x578aab] emacs[0x5b7ef4] emacs[0x57b551] emacs[0x578aab] emacs[0x5b7ef4] emacs[0x57b551] emacs[0x578aab] emacs[0x5b7ef4] emacs[0x578aab] emacs[0x5b7ef4] emacs[0x578aab] emacs[0x57a93c] emacs[0x578b2c] emacs[0x5b7ef4] emacs[0x578aab] emacs[0x5b7ef4] emacs[0x57b551] emacs[0x578aab] emacs[0x57a93c] emacs[0x578b2c] emacs[0x5b7ef4] emacs[0x578aab] emacs[0x578c1e] ... [2]- Aborted (core dumped) emacs foo.mod Version-Release number of selected component: 1:emacs-26.2-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: emacs foo.mod crash_function: emacs_abort executable: /usr/bin/emacs-26.2 journald_cursor: s=7ac1a5a53313482fb0ae08610619ef9c;i=1324ec;b=1ba85be1235143d3ac6babecdd66f24b;m=344e34bb38;t=589458265ba9a;x=6c3f2fa3c0a23e4 kernel: 5.0.16-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1591222
Created attachment 1571043 [details] File: backtrace
Created attachment 1571044 [details] File: cgroup
Created attachment 1571045 [details] File: core_backtrace
Created attachment 1571046 [details] File: cpuinfo
Created attachment 1571047 [details] File: dso_list
Created attachment 1571048 [details] File: environ
Created attachment 1571049 [details] File: limits
Created attachment 1571050 [details] File: maps
*** Bug 1729582 has been marked as a duplicate of this bug. ***
*** Bug 1739094 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.