Bug 486695

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 333196 [details]
X.org log

Having disabled Desktop Effects, it hasn't occurred for a few days, so I'm willing to bet that compositing (at least using OpenGL) is the trigger.

When it happens, can we get /var/log/Xorg.0.log (just to be sure, we have the right one), /var/log/messages, and /var/log/dmesg, please?

Well, I think i managed to get the files you need. This time while grabbing the files i switched to text mode and back to graphical mode and noted that KDE was responsive again. 

I know that 'cause my CPU plasmoid starts to plot again CPU usage. When it happens, the plasmoid looks like those equipments that monitor heartbeat and then the subject dies, just a straight line.

But this responsiveness don't take too much and any new open application makes the CPU die again. Too sad.

Created attachment 333466 [details]
Xorg.0.log when it happens

Created attachment 333467 [details]
messages a few minutes before it happens

Created attachment 333468 [details]
dmesg when it happnes

Ah! kernel oopsed when I switched to text mode and back again to graphical mode.

Using Fedora 11 beta full updated with kde 4.2.2 and desktop effects activated and i can't see this bug anymore.

I'll test again over the next few days. I saw the window corruption bug and turned it off again.

It just occurred here. Still not fixed with KDE 4.2.2/Qt 4.5.0.

Are you using rawhide? Rawhide has a new Xorg stack with an updated intel driver.

Ah. This is F10. My Rawhide machine has an nVidia. I'll test again when I upgrade this machine in a few weeks.

Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, including Intel driver, which may have resolved this issue.
To be more precise, Intel has undergone a major rewrite during Fedora 10, 11 and 12 cycles, and whole driver is working a lot better now. Users who have experienced this problem are encouraged to retry with at least Fedora 12 Beta and see if the issue is still relevant.

Please, if you experience this problem on Fedora 12 Beta or up-to-date system running Rawhide, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

We hope to see how many older bugs in Intel driver are still relevant today, in hope that most of them were fixed in rewrite process.

[This is a bulk message for all open Fedora 10 i810-related bugs (39 of them are still open). I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

No i don't see this problem anymore. But i'm having one issue that acording to the documentation i found is related to intel driver. I didn't do a very compreensive search, chances that i'm wrong. 

It's related to suspend/resume not working as expected, the computer seems to come back from suspend state, but in some case keyboard is not working, neither mouse. And now after the last kernel update the screen is always black 
after a resume. 

Other thing i noted is when alternating between the graphical mode and the cosole, i can't get back to graphical mode, all is black. 

I already opened a bug report about the keyboard and mouse, here it is 
https://bugzilla.redhat.com/show_bug.cgi?id=529986. And here are the bug and the doc that made me relate the black screen with the intel driver, https://bugzilla.redhat.com/show_bug.cgi?id=473542
and http://fedoraproject.org/wiki/Common_kernel_problems#Suspend.2FResume_to_RAM_failure. 

I'm attaching the dmesg output while runing pm-suspend and resuming my Dell Vostro 1400. The kernel version i'm using is 2.6.31.5-117.fc12.i686.PAE. Anything else i can do? 

Thank you.

Created attachment 367770 [details]
dmesg output while running pm-suspend and then resuming

I haven't encountered this for quite some time and I've had effects on for weeks at a time (which is the only time this got triggered before). I'd say it's fixed.

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

Thank you for your bug report.

We are sorry, but the Fedora Project is will soon stop longer releasing bug fixes or any other updates for this version of Fedora. There were so many changes between Fedora 10 and Fedora 12 in Intel driver and X.Org that it's very likely that this bug is fixed. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora (version 12), which is available from:

http://fedoraproject.org/get-fedora