Created attachment 327040 [details] xorg config Description of problem: System - Thinkpad T60p (ATI V5200), radeonhd driver If compiz/emerald is enabled and system is suspended, then resumed. then upon resume system returns to login desktop, not to existing session/screensaver. If compiz etc NOT enabled then system correctly resumes with existing desktop Occurred with original radeonhd/kernel levels, also occurs with latest from koiji Some Current rpms kernel-PAE-2.6.27.9-157.fc10.i686 xorg-x11-drv-radeonhd-1.2.4-1.1.20081212git.fc10.i386 xorg-x11-server-common-1.5.3-5.fc10.i386 compiz-0.7.6-17.fc10.i386 No exceptions observed in /etc/X11/Xorg.0.log.old, nor kernel messages from dmesg. PM logs don't appear interesting either Version-Release number of selected component (if applicable): Some Current rpms kernel-PAE-2.6.27.9-157.fc10.i686 xorg-x11-drv-radeonhd-1.2.4-1.1.20081212git.fc10.i386 xorg-x11-server-common-1.5.3-5.fc10.i386 compiz-0.7.6-17.fc10.i386 How reproducible: Occurs every time Steps to Reproduce: 1.login, Enable compiz 2.suspend/resume 3.get bounced to login screen Actual results: Bounced to login screen Expected results: Show screensaver/existing session Additional info:
Created attachment 327041 [details] previous log file from X
Created attachment 327042 [details] xorg log
Created attachment 327043 [details] pm suspend log
Repeated same test with "radeon" driver using Driver "radeon" Option "RenderAccel" "true" Option "AccelMethod" "EXA" Option "EnablePageFlip" "on" Option "DynamicClocks" "1" Option "AccelDFS" "1" Option "DMAForXv" "1" Option "GARTSize" "64" Option "EnableDepthMoves" "on" Option "DRI" "true" Option "VideoKey" "0x01" and get an interesting result 8151 frames in 5.0 seconds = 1630.006 FPS 8141 frames in 5.0 seconds = 1628.157 FPS 8144 frames in 5.0 seconds = 1628.779 FPS 8149 frames in 5.0 seconds = 1629.685 FPS ^C // SUSPEND // RESUME bash-3.2$ glxgears 1341 frames in 5.0 seconds = 268.118 FPS 1333 frames in 5.0 seconds = 266.471 FPS 1291 frames in 5.0 seconds = 258.044 FPS This is with just metacity. Could there be some DRI re-init issue here?
475193 may be related
That is bug 475193 (so that we a link)
Now seems to be working with xorg-x11-server-Xorg-1.6.0-2.fc11.i586 kernel-PAE-2.6.29-0.159.rc6.git3.fc11.i686 kernel-PAE-2.6.29-0.176.rc6.git5.fc11.i686 compiz-0.7.8-14.fc11.i586 for the first time since F9 :-)
& xorg-x11-drv-ati-6.11.0-1.fc11.i586
This (or something similar) seems to be affecting F11 with the Intel driver.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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
Closing per comment 7 and comment 8.