Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Desktop effects sometimes has screen corruption coming out of suspend. I will attach an image that illustrates what I mean. Version-Release number of selected component (if applicable): Full 2.6.22.1-41.fc7, all packages up to date as of date of this report. How reproducible: Sometimes, not always. Happens to me sometimes when I suspend at night and then the next morning turn on. Steps to Reproduce: 1. Have desktop effects turned on 2. Suspend 3. Restart Actual results: Sometimes gives results as in the attached picture Expected results: Shouldn't show screen corruption
Created attachment 160543 [details] screen shot illustrating the screen corruption
Created attachment 160544 [details] the xorg.conf file - which is completely default
Created attachment 160545 [details] the Xorg.0.log file
Created attachment 160546 [details] the /var/log/messages
I have the same problem on my Dell Latitude D610, with ATI Mobility Radeon X300. The bug is 100% repeatable: all window decorations are corrupted when coming out of suspend. My solution is to force them to repaint using Alt+Tab or Ctrl+Alt+Left or some other keystroke that triggers beryl. I can attach confs and logs if needed.
Created attachment 160775 [details] Corrupt window decorations. Screen shot taken after resuming from suspend, before any interaction with beryl.
*** This bug has been marked as a duplicate of 210602 ***
Per https://bugzilla.redhat.com/show_bug.cgi?id=210602#c12 reopening this bug. David, bug 210602 was against Rawhide. Could you please upgrade both your /etc/X11/xorg.conf and /var/log/Xorg.0.log with Rawhide computer? Also could you try please to run X without any /etc/X11/xorg.conf whatsoever? What happens then?
*** Bug 210602 has been marked as a duplicate of this bug. ***
Created attachment 226301 [details] Xorg.0.log I don't have rawhide running here as from what I understand it isn't necessarily stable, and my computer requires stability as I do my work on it. But with kernel 2.6.22.9-91.fc I still see graphical corruption when running X without any /etc/X11/xorg.conf and I have updated the attached Xorg.0.log with that log. I also see https://bugzilla.redhat.com/show_bug.cgi?id=250683 on suspend which is a real pain because every time I come out of suspend I have to unplug and re-plug my external keyboard for either keyboard to work.
OK, we will stay with F7.
This problem still apparent in f8, kernel 2.6.23.1-49.fc8
Fixed for me. F8, kernel-2.6.23.1-49.fc8, compiz-0.6.2-3.fc8. Running compiz-manager --replace & emerald --replace &
Created attachment 260561 [details] Image illustrating screen corruption still present in f8 I'm running identical software versions as Richard Guest above and the corruptions still occur when coming out of suspend. Image attached.
I see this as well in current F8: kernel-2.6.24.4-64.fc8 compiz-0.6.2-3.fc8 xorg-x11-drv-ati-6.8.0-4.fc8 The borders and effect areas (like shadows) are always somewhat or a lot corrupted when returning from suspend or hibernate.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 '8'. 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 8'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 8 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
I don't know about you guys, but I'm seeing this again in F9... compiz-0.7.6-3.fc9.1 emerald-0.7.6-1.fc9 kernel-2.6.27.5-41.fc9 xorg-x11-drv-ati-6.8.0-19.fc9 Will attach screenshot...
Created attachment 324792 [details] Screenshot of corruption in F9 I still get this after resuming from suspend in F9.
David, Richard, Could you test current F10 without any xorg.conf and report ? If you can reproduce the bug in current F10 : * please try using nomodeset in the kernel command line * please try the latest xorg-x11-drv-ati build in Koji : http://koji.fedoraproject.org/koji/buildinfo?buildID=80819
I've given up on compiz on radeon hardware. Currently it's absolutely dog slow and crashes X when I resume from suspend...
(In reply to comment #20) > I've given up on compiz on radeon hardware. > > Currently it's absolutely dog slow and crashes X when I resume from suspend... DOes it mean, that we should close this bug as INSUFFICIENT_DATA?
(In reply to comment #21) > DOes it mean, that we should close this bug as INSUFFICIENT_DATA? I'll leave that call up to David, as he's the original bug reporter. I'll simply ensure that the next laptop I get has a nvidia chipset...
> I'll simply ensure that the next laptop I get has a nvidia chipset... I won't even comment on that. :)
I've given up on F10... it is too broken to use in many ways on my hardware. Video has corruption, sound is broken, etc. F8 was quite good, but has lost support so I'm not using it any more either. You're welcome to close this case as INSUFFICIENT DATA.
I am sorry to hear this. Hopefully we will be able to help you in any future version. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.
This has been fixed on F10 with the latest kernel and radeon driver. I don't know exactly when it was fixed, but now that it doesn't hang on resume, it doesn't have the random bits any more.