Created attachment 693002 [details] Portion of Cinnamon desktop showing window rendering issue Description of problem: When using the Cinnamon desktop, windows have a rectangular chunk missing on the upper left corner as if some of the window elements are not being rendered correctly. This problem comes and goes at random times. Sometimes it is evident on only one window on the desktop, other times it shows on some or all windows. I've not been able find a way to reliably reproduce it but I see the problem every day, multiple times per day; I'd say it's evident about 75% or more of the time. Version-Release number of selected component (if applicable): How reproducible: Most of the time in varying degrees Steps to Reproduce: 1. install Cinnamon desktop 2. open windows 3. Actual results: Windows often render incorrectly Expected results: Windows render correctly Additional info: I'm attaching a screen shot that demonstrates the problem on two windows.
This is a graphics driver issue.
Interesting, must be a recent change in the driver as I've been running Fedora F14/F15 on this box for years with no similar problems. Didn't notice it until installing F18 recently. In any case, here's some info on my video card that might help diagnose the bug: VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV380 [Radeon X600 (PCIE)] model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ cpu MHz : 2310.358 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ cpu MHz : 2310.358 dimensions: 1920x1200 pixels (508x317 millimeters) depth of root window: 24 planes direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV370 OpenGL version string: 2.1 Mesa 9.0.1
This is a duplicate of #706761 (even though the other report uses GNOME Shell and this one uses Cinnamon, the rest of the stack is the same and that's where the problem is).
Can you reproduce this with Mesa 9.1? It's available in F18 updates.
(In reply to comment #4) > Can you reproduce this with Mesa 9.1? It's available in F18 updates. Yes, I still see the problem. According to Yum, here's what I'm current using: Loaded plugins: langpacks, presto, refresh-packagekit Installed Packages mesa-dri-drivers.x86_64 9.1-3.fc18 @updates mesa-dri-filesystem.x86_64 9.1-3.fc18 @updates mesa-libEGL.x86_64 9.1-3.fc18 @updates mesa-libGL.x86_64 9.1-3.fc18 @updates mesa-libGLU.x86_64 9.0.0-1.fc18 @anaconda mesa-libgbm.x86_64 9.1-3.fc18 @updates mesa-libglapi.x86_64 9.1-3.fc18 @updates mesa-libxatracker.x86_64 9.1-3.fc18 @updates
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.