Bug 695611

Summary: [abrt] xorg-x11-server-Xorg-1.7.7-26.el6_0.3: ddxGiveUp: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: cww, tpelka, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-29 18:39:29 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
Backtrace, Dissassembly none

Description Siddharth 2011-04-12 07:44:20 UTC 
Description of problem:

abrt version: 1.1.13
Attached file: backtrace
cmdline: /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-HGrxYo/database -nolisten tcp vt1
component: xorg-x11-server
crash_function: ddxGiveUp
executable: /usr/bin/Xorg
kernel: 2.6.32-71.24.1.el6.i686
rating: 0
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
time: 1302531970
uid: 0


Version-Release number of selected component (if applicable):

architecture: i686
xorg-x11-server-Xorg-1.7.7-26.el6_0.3
Red Hat Enterprise Linux Server release 6.0 (Santiago)

How reproducible:
Random Crash.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Xorg-server was killed

Expected results:
Xorg-server should not killed

Additional info:
Comment 1 Siddharth 2011-04-12 08:00:29 UTC 
Created attachment 491422 [details]
Backtrace, Dissassembly
Comment 3 RHEL Program Management 2011-04-12 08:17:43 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Adam Jackson 2011-05-25 17:11:41 UTC 
This backtrace is completely improbable.  What were you doing when this crashed?  Is it at all reproducible?  Do you get different backtraces from subsequent crashes?
Comment 5 Tomas Pelka 2011-05-30 14:21:03 UTC 
Agree with Adam,

please provide more info.

Also please try on latest RHEL6.1 Beta if possible.
Comment 8 Adam Jackson 2011-06-29 18:39:29 UTC 
No updates in over one month, closing.  If this is still an issue please provide the information requested in comment #4.