Version-Release number of selected component: emacs-1:27.1-3.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-emacs-6105.scope cmdline: emacs crash_function: emacs_abort executable: /usr/bin/emacs-27.1 journald_cursor: s=f6c981e52e7d44a8a3afcb41a6747bc8;i=26766;b=c9457ae536244597ae2b1843a1354b70;m=7753d558;t=5be69c4b9beba;x=44e51e820dfdc041 kernel: 5.11.9-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1711721
Created attachment 1766978 [details] File: backtrace
Created attachment 1766979 [details] File: core_backtrace
Created attachment 1766980 [details] File: cpuinfo
Created attachment 1766981 [details] File: dso_list
Created attachment 1766982 [details] File: environ
Created attachment 1766983 [details] File: limits
Created attachment 1766984 [details] File: maps
Created attachment 1766985 [details] File: mountinfo
Created attachment 1766986 [details] File: open_fds
Created attachment 1766987 [details] File: proc_pid_status
Do you happen to recall how the crash occurred? The backtrace looks like the connection was lost to the X server, when emacs crashed.
I do not remember specifically, Emacs just stopped responding in the background. I am running Wayland though. Since the report, the COPR that uses native GTK support has provided F34 builds and moved to that version (which I used in F33 too).
@dueno Do you think we can make this bug public so that we can send this upstream? Not sure if they'll be able to use this, but maybe they might have an idea.
I am ok with making the bug public, yes.
(In reply to Sebastián Monía from comment #14) > I am ok with making the bug public, yes. Can you change its visibility? I don't appear to be able to do that.
*** Bug 1978339 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I wasnt using emacs at this moment, it was idle. Im pretty sure it crashed cuz gnome-shell crashed at same time, report generation failed for that - low information value iirc. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-61977c82-8dfa-4c4e-b8d4-fb066ce2e916.scope cmdline: emacs include/linux/dynamic_debug.h crash_function: emacs_abort executable: /usr/bin/emacs-27.2 journald_cursor: s=8819bcd740424051846977471e8f5346;i=11bf0;b=1956927167624ec9b546f18ad5981b5b;m=f274d7689c;t=5c857f337abca;x=3e69f030cb17a045 kernel: 5.14.0-rc1-lm1 package: emacs-1:27.2-3.fc34 reason: emacs-27.2 killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.