Bug 1591222

Summary: [abrt] emacs: emacs_abort(): emacs-26.1 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Peter Baker <dr_pete_baker>
Component: emacsAssignee: Jan Synacek <jsynacek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: jkeating, jonathan.underwood, jsynacek, msekleta, phracek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/01088b4d0cb17a59012e31bd6012aed6cf3d2112
Whiteboard: abrt_hash:57397bb73c674577a190535cd826f1dedb8c637a;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 20:38:59 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: cgroup
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 Peter Baker 2018-06-14 10:22:29 UTC 
Description of problem:
Installed emacs 26.1 a few minutes ago
Started emacs and X crashed
Exact same problem I had when running emacs beta from sourcewith NVIDIA card/drivers - changed drivers but didn't help so just 
stuck with standard system emacs. Now that's broken so will have to downgrade. It may just be driver/card
combination  as don't seem to have any problem with similar setup at work but machine is newer

Thanks
Peter

Version-Release number of selected component:
1:emacs-26.1-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        emacs
crash_function: emacs_abort
executable:     /usr/bin/emacs-26.1
journald_cursor: s=c236fddbe28c4410ab0ecc18fbdc38a1;i=bb6798;b=ee4deebd154f48a08c3e635d735eb1cb;m=8320e3f2;t=56e97369ca87e;x=8c6fb0d17078e374
kernel:         4.16.14-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Peter Baker 2018-06-14 10:22:36 UTC 
Created attachment 1451275 [details]
File: backtrace
Comment 2 Peter Baker 2018-06-14 10:22:38 UTC 
Created attachment 1451276 [details]
File: cgroup
Comment 3 Peter Baker 2018-06-14 10:22:40 UTC 
Created attachment 1451277 [details]
File: core_backtrace
Comment 4 Peter Baker 2018-06-14 10:22:41 UTC 
Created attachment 1451278 [details]
File: cpuinfo
Comment 5 Peter Baker 2018-06-14 10:22:43 UTC 
Created attachment 1451279 [details]
File: dso_list
Comment 6 Peter Baker 2018-06-14 10:22:45 UTC 
Created attachment 1451280 [details]
File: environ
Comment 7 Peter Baker 2018-06-14 10:22:47 UTC 
Created attachment 1451281 [details]
File: limits
Comment 8 Peter Baker 2018-06-14 10:22:50 UTC 
Created attachment 1451282 [details]
File: maps
Comment 9 Peter Baker 2018-06-14 10:22:52 UTC 
Created attachment 1451283 [details]
File: mountinfo
Comment 10 Peter Baker 2018-06-14 10:22:54 UTC 
Created attachment 1451284 [details]
File: open_fds
Comment 11 Peter Baker 2018-06-14 10:22:55 UTC 
Created attachment 1451285 [details]
File: proc_pid_status
Comment 12 Ben Cotton 2019-05-02 21:35:09 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.
Comment 13 Ben Cotton 2019-05-28 20:38:59 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.