Bug 597031

Summary: [abrt] crash in xorg-x11-server-Xorg-1.8.0-12.fc13: Process /usr/bin/Xorg was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: ringwald
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:93c34d11c4b6e5db78f63a2f610bbf524f4ab580
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 16:52:04 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

Description ringwald 2010-05-28 00:17:19 UTC
abrt 1.1.0 detected a crash.

architecture: i686
cmdline: /usr/bin/X -br -nolisten tcp :0 vt1 -auth /var/run/kdm/A:0-4gGzWa
component: xorg-x11-server
executable: /usr/bin/Xorg
global_uuid: 93c34d11c4b6e5db78f63a2f610bbf524f4ab580
kernel: 2.6.33.4-95.fc13.i686
package: xorg-x11-server-Xorg-1.8.0-12.fc13
rating: 0
reason: Process /usr/bin/Xorg was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1275003251-1548/coredump is truncated: expected core file size >= 40091648, found: 31502336.
warning: core file may not match specified executable file.
[New Thread 1548]
Cannot access memory at address 0xb78c83d8

Thread 1 (Thread 1548):
Cannot access memory at address 0xbfe75e8c
Cannot access memory at address 0xb78c83d8
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax            0xaa87c0	11175872
ecx            0x0	0
edx            0x0	0
ebx            0xbeb104	12497156
esp            0xbfe75e8c	0xbfe75e8c
ebp            0xbfe75ef4	0xbfe75ef4
esi            0xbfe75fe8	-1075355672
edi            0xbfe75fe8	-1075355672
eip            0xbe4d66	0xbe4d66
eflags         0x13246	[ PF ZF IF #12 #13 RF ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
No function contains program counter for selected frame.

Comment 1 ringwald 2010-05-28 00:17:21 UTC
Created attachment 417428 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-02 13:09:25 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 3 Bug Zapper 2011-06-27 16:52:04 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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