Bug 707210

Summary: [abrt] emacs-1:23.2-7.fc14: Process /usr/bin/emacs-23.2 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Tero Nieminen <ttn>
Component: emacsAssignee: Karel Klíč <kklic>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jonathan.underwood, kklic, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8d00609926b85cab7657cac6d8dbc0b25d7811d1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 13:54:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Tero Nieminen 2011-05-24 12:10:02 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 11245 bytes
cmdline: emacs
component: emacs
Attached file: coredump, 15540224 bytes
executable: /usr/bin/emacs-23.2
kernel: 2.6.35.13-91.fc14.i686
package: emacs-1:23.2-7.fc14
rating: 4
reason: Process /usr/bin/emacs-23.2 was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1306238132
uid: 500

How to reproduce
-----
1. Start emacs from std menu
2. Emacs starts and xserver crashes
3. Login screen comes back

Comment 1 Tero Nieminen 2011-05-24 12:10:05 UTC
Created attachment 500594 [details]
File: backtrace

Comment 2 Tero Nieminen 2011-05-25 09:40:16 UTC
This may be a bug in the F14 (radeon) X server: Abrt just reported it (this time) as an emacs crash (and emacs is not the only application causing my X server to crash).

Comment 3 Tero Nieminen 2011-06-13 12:44:48 UTC
After fiddling with xorg.conf (mainly /etc/X11/xorg.conf) I got rid of the crash problem (the crashes used to occur both with vesa and radeon drivers).  I qurss something didn't quite work with my upgrade path (I skipped F13). So I quess, case closed..

Comment 4 Fedora End Of Life 2012-08-16 13:54:34 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping