| Author |
Message |
dexterus
|
|
Post subject:
 Posted: 11.08.2011, 01:28
|
|
Joined: 2010-09-16
Posts: 16
Status: Offline
|
|
|
daniel_ro wrote:
ok, how to downgrade then? to 2.68. Any idea ?could not find on google.
i don't think that would help, since the problem is with x server. i'm afraid all we can do is to sit and hope for a prompt patch (at least those of us who are not very skillfull in programming  ). |
|
|
| |
|
|
|
 |
|
daniel_ro
|
|
|
Post subject: poor rendering, x or mesa ?
Posted: 11.08.2011, 06:09
|
|
Joined: 2011-01-07
Posts: 51
Location: Bacau - Romania
Status: Offline
|
|
if X is the problem howcome other distros dont display this ugly lines?
I think it better a conflict with mesa driver of something...
it is very annoying and cannot use my computer like this. I am forced to change the distro, because of this error display... cant work like this! 
is it on kde only or xfce as well ? |
|
|
| |
|
|
|
|
|
pumrel
|
|
|
Post subject: RE: poor rendering, x or mesa ?
Posted: 13.08.2011, 10:58
|
|
Joined: 2010-09-14
Posts: 117
Location: Czech Republic
Status: Offline
|
|
| I think it's only KDE. I don't have the issue with aptosid xfce. Also, changing distro would not help, in my opinion, as I had the same problem with Chakra for example. |
_________________
Petr
|
| |
|
|
|
|
|
dexterus
|
|
|
Post subject:
Posted: 31.08.2011, 20:07
|
|
Joined: 2010-09-16
Posts: 16
Status: Offline
|
|
i must say that after having certain desktop effects in kde enabled (namely: fade, logout and minimize animation), which i had all disabled, and animation speed set to normal, the severity of the problem reduced significantly.
also, desktop effects render quite smoothly. actually, smoother and faster than ever before on this ancient radeon 9200. so, looks like xserver team did a really good job. |
|
|
| |
|
|
|
|
|
DeepDayze
|
|
|
Post subject:
Posted: 02.09.2011, 17:22
|
|
Joined: 2010-09-11
Posts: 609
Location: USA
Status: Offline
|
|
| Old Radeon 7500 here on a Thinkpad T42..the artifacts are largely gone from here too. Whatever bug that caused this was somehow fixed |
|
|
| |
|
|
|
|
|
|
