Description of problem: Windows occasionally experience corruption to their content that requires moving the window in order to redraw. Sometimes, a window will simply fill with e.g. many copies of the scrollbar from left to right until it is moved off screen and back or otherwise caused to redraw itself. KMS is enabled. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.9.0-9.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1. Login to a gnome-session 2. Use various software 3. Windows become frequently corrupted and require redrawing Actual results: Windows have corrupted contents Expected results: Windows do not have corrupted contents Additional info: Here is the information about the graphics card on this system: 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200] (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T60p Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at 2000 [size=256] Region 2: Memory at ee100000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at ee120000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. Also, please, what's the version of your kernel? We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 447626 [details] xorg.conf
Created attachment 447627 [details] Xorg.0.log
Created attachment 447629 [details] Xorg.9.log
Created attachment 447630 [details] dmesg
Created attachment 447631 [details] messages
The kernel version is 2.6.36-0.21.rc4.git1.fc15.x86_64
http://www.youtube.com/watch?v=L4ORbAvbm9E http://www.youtube.com/watch?v=8JvtEjfuNIE
These walk you through the issues. The second video explicitly shows the color corruption.
As noted on the video, restarting X does "fix" this. So it's not permanent. The VT switch is still corrupted (tty2), but the graphical Xorg session is ok after a logout/login.
is there any particular reason to suspect this is a general X bug and not specific to the ati driver? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
well the logs are for the vesa driver, so its not an -ati bug. not sure why vesa would be used, probably should try with -ati. I think pixman has a bug triggered by new glibc that we need to track down.
(In reply to comment #12) > I think pixman has a bug triggered by new glibc that we need to track down. So, shouldn't we reassign this to pixman then? Matěj
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.