Bug 999565

Summary: [abrt] xorg-x11-server-Xorg-1.14.2-9.fc19: exit: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Hebert Silva <hebert.soares>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: hebert.soares, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f4645feaeed3b980737b3b05a303dab23ddac2b1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:51:56 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
File: cgroup
none
File: core_backtrace
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Hebert Silva 2013-08-21 14:58:40 UTC
Description of problem:
Shutting down X windows server

Version-Release number of selected component:
xorg-x11-server-Xorg-1.14.2-9.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-mPRGtc
crash_function: exit
executable:     /usr/bin/Xorg
kernel:         3.10.5-201.fc19.i686.PAE
uid:            0

Truncated backtrace:
Thread no. 1 (3 frames)
 #13 exit at exit.c:99
 #14 __libc_start_main at libc-start.c:292
 #15 _start

Comment 1 Hebert Silva 2013-08-21 14:58:47 UTC
Created attachment 788906 [details]
File: backtrace

Comment 2 Hebert Silva 2013-08-21 14:58:50 UTC
Created attachment 788907 [details]
File: cgroup

Comment 3 Hebert Silva 2013-08-21 14:58:54 UTC
Created attachment 788908 [details]
File: core_backtrace

Comment 4 Hebert Silva 2013-08-21 14:58:58 UTC
Created attachment 788909 [details]
File: environ

Comment 5 Hebert Silva 2013-08-21 14:59:01 UTC
Created attachment 788910 [details]
File: limits

Comment 6 Hebert Silva 2013-08-21 14:59:03 UTC
Created attachment 788911 [details]
File: maps

Comment 7 Hebert Silva 2013-08-21 14:59:07 UTC
Created attachment 788912 [details]
File: open_fds

Comment 8 Hebert Silva 2013-08-21 14:59:12 UTC
Created attachment 788913 [details]
File: proc_pid_status

Comment 9 Fedora End Of Life 2015-01-09 19:32:46 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 10 Fedora End Of Life 2015-02-17 16:51:56 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.