Bug 643701

Summary: [xorg-x11-drv-ati] black window when running glxgears after resume from suspend on ATI Radeon X800 SE (R430)
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-11 10:05:06 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
Xorg.0.log
none
Output of 'dmesg'. none

Description Joachim Frieben 2010-10-17 12:55:18 UTC 
Description of problem:
When running glxgears after resume from suspend on a system equipped with an ATI Radeon X800 SE (R430), all I get is a black window. Moreover, it does not react to keyboard input, namely pressing <ESC>. The application windows just stays there, even after pressing <ctrl-C> in the terminal window from which it had been launched.
 
Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Run glxgears.
2. Suspend and resume.
3. Run glxgears.
  
Actual results:
Application window is black and does not respond to keyboard input.

Expected results:
Application window shows turning gears.

Additional info:
No desktop effects were enabled during the X session.
Comment 1 Joachim Frieben 2010-10-17 12:55:55 UTC 
Created attachment 453916 [details]
Xorg.0.log
Comment 2 Joachim Frieben 2010-10-17 12:56:21 UTC 
Created attachment 453917 [details]
Output of 'dmesg'.
Comment 3 Joachim Frieben 2010-12-11 10:05:06 UTC 

*** This bug has been marked as a duplicate of bug 643700 ***