Red Hat Bugzilla – Bug 499845
Corruptions in 2D graphics with R600 (Radeon HD 3650)
Last modified: 2010-03-02 12:50:42 EST
Description of problem:
With the free driver, I get some random small-ish corruption in some Qt widgets and Spotify (under Wine), which while unrelated, is also showing currupted graphics in its titlebar and is missing many of the widgets on this computer.
The most certain way to reproduce this corruption is to select Plastique as the style in Qt (The Arora browser overrides Oxygen with Plastique due to some problems with the Oxygen style) and write something in a text field. I'll add a screenshot that shows what it looks like in Arora. The bug can also be reproduced in programs besides Arora if the Plastique style is selected globally. The bug doesn't appear on computers with different graphics hardware, like my laptop with an old Radeon 7500.
Version-Release number of selected component (if applicable):
Always on this computer.
Steps to Reproduce:
1. Log into KDE on a computer with Fedora 11 and R600-based video hardware.
2. Open Arora or some other program that uses the Plastique Qt style.
3. Write something to a text field somewhere.
The text field is filled with black garbage.
Only usual well-drawn letters appear in the text field.
Created attachment 343101 [details]
Screenshot of the corruption in the Arora browser
Created attachment 343102 [details]
Xorg.0.log from the computer where this happens
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Probably a more specific way to reproduce:
1. Install Qt 4 and arora.
2. Use qtconfig-qt4 to set the qt program style to Cleanlooks. Save settings,
3. arora google.com
4. Write something to the search text field.
On my machine, this always results in the search field contents being drawn over with a black block of pixels.
Identifier "primary graphics card"
Option "RenderAccel" "off"
I tried to use that xorg.conf to turn EXA off. Even with these settings, the corruption persists. Am I doing something wrong, or should I file a bug against the driver for not respecting the setting?
I'll post the Xorg.0.log shortly as an attachment.
Created attachment 349564 [details]
Xorg.0.log from a machine on which RenderAccel was supposed to have been turned off.
I see the same corruption on my X1650. This bug sounds very similar, on an
Sure seems like a KDE or Qt bug to me.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, 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.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. 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.]
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Sorry for not responding to this earlier.
However, I have not encountered this bug in a few months. At least for F12, I can consider it fixed. Thanks, developers :-)
Thank you for letting us know.