Bug 2110140

Summary: [abrt] emacs: emacs_abort(): emacs-28.1 killed by SIGABRT
Product: [Fedora] Fedora Reporter: nik <nikita>
Component: emacsAssignee: Daiki Ueno <dueno>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: dan.cermak, dimhen, dueno, gordon.messmer, ibganev, jkeating, jonathan.underwood, msekleta, phracek, robinlee.sysu, swt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/96a2153e638d6bde0c962e613fea62cbe7d4a933
Whiteboard: abrt_hash:7e79cd0cdae1f9c4d45600c842e8422adea23e08;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 15:56:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description nik 2022-07-23 21:35:06 UTC 
Description of problem:
Started up Emacs with this config: https://github.com/nikital/dotfiles/tree/master/emacs/.emacs.d

Version-Release number of selected component:
emacs-1:28.1-2.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-emacs-8962.scope
cmdline:        /usr/bin/emacs --batch -l /tmp/emacs-async-comp-lsp-mode-zG2Ryp.el
crash_function: emacs_abort
executable:     /usr/bin/emacs-28.1
journald_cursor: s=d1cea57d8f864d7ca2af6326c3e7bc5b;i=717a;b=5af97fe0e8634152981b9ba782e29989;m=88fdc345;t=5e47ea4e6682a;x=fea7e73f6467ca7c
kernel:         5.18.11-200.fc36.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1626318
Comment 1 nik 2022-07-23 21:35:10 UTC 
Created attachment 1898974 [details]
File: backtrace
Comment 2 nik 2022-07-23 21:35:11 UTC 
Created attachment 1898975 [details]
File: core_backtrace
Comment 3 nik 2022-07-23 21:35:12 UTC 
Created attachment 1898976 [details]
File: cpuinfo
Comment 4 nik 2022-07-23 21:35:13 UTC 
Created attachment 1898977 [details]
File: dso_list
Comment 5 nik 2022-07-23 21:35:15 UTC 
Created attachment 1898978 [details]
File: environ
Comment 6 nik 2022-07-23 21:35:16 UTC 
Created attachment 1898979 [details]
File: limits
Comment 7 nik 2022-07-23 21:35:17 UTC 
Created attachment 1898980 [details]
File: maps
Comment 8 nik 2022-07-23 21:35:18 UTC 
Created attachment 1898981 [details]
File: mountinfo
Comment 9 nik 2022-07-23 21:35:19 UTC 
Created attachment 1898982 [details]
File: open_fds
Comment 10 nik 2022-07-23 21:35:20 UTC 
Created attachment 1898983 [details]
File: proc_pid_status
Comment 11 Luca Giuzzi 2022-08-18 12:05:09 UTC 
Similar problem has been detected:

emacs crashed on startup
the configuration is somehow heavily configured

reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-daf4f9ff-8710-4a3d-b0a0-5cb53fe0afec.scope
cmdline:        /usr/bin/emacs --batch -l /tmp/emacs-async-comp-dash-3DeuXY.el
crash_function: emacs_abort
executable:     /usr/bin/emacs-28.1
journald_cursor: s=38ed9aa7bf334c179e2f3f58d069a740;i=d9e62;b=3dcf58d7766a4ea48a0e43312e72f731;m=237eacba6;t=5e681798ab020;x=f8bb9b49773eb76f
kernel:         5.18.17-200.fc36.x86_64
package:        emacs-1:28.1-2.fc36
reason:         emacs-28.1 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 Dan Čermák 2022-08-18 13:16:26 UTC 
Is the crash reproducible?
Comment 13 nik 2022-08-22 18:22:12 UTC 
No, it happened once
Comment 14 Ivan Ganev 2022-10-25 22:44:55 UTC 
*** Bug 2137703 has been marked as a duplicate of this bug. ***
Comment 15 Ben Cotton 2023-04-25 17:39:11 UTC 
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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.
Comment 16 Ludek Smid 2023-05-25 15:56:37 UTC 
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.