Bug 229983 - Strange painting artifacts in applications
Summary: Strange painting artifacts in applications
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-08 19:39 UTC by Alexey Chernov
Modified: 2010-03-10 08:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of the problem (231.26 KB, image/png)
2010-03-08 19:40 UTC, Alexey Chernov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Chernov 2010-03-08 19:39:42 UTC
Version:            (using KDE 4.4.1)
Compiler:          GCC 4.4.3 Target: x86_64-unknown-linux-gnu Configured with: ../gcc-4.4.3/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran --disable-multilib --disable-bootstrap
OS:                Linux
Installed from:    Compiled From Sources

I suffer of strange painting artifacts on opened windows of several applications (see the screenshot). Most frequently it appears when switching to window using Alt+Tab. Seems that some areas of window aren't redrawn. If to scroll down and then up, everything become ok. Looks VERY similar to bug #187356 (please duplicate it if it's so). But in my case Xserver version is 1.7.x (I've tried 1.7.1 to 1.7.5, no changes) and Qt 4.6.2.
Comment 1 Alexey Chernov 2010-03-08 19:40:18 UTC
Created attachment 41453 [details]
Screenshot of the problem
Comment 2 Christoph Feck 2010-03-09 03:56:18 UTC
I doubt this is a KDE problem, as this looks more like a problem with the graphics drivers, but KWin developers may know a solution.
Comment 3 Martin Flöser 2010-03-09 09:15:32 UTC
I think it is a driver bug, too. But to be sure: from your screenshot it looks like you do not use desktop effects? What is your graphics driver?
Comment 4 Alexey Chernov 2010-03-09 09:23:32 UTC
It's radeonhd-1.3.0 now. I also tried different versions of xf86-video-ati (6.12.x branch) with the same effect. According to bug #187356 it could be something with Xserver, but they reported it was fixed in 1.6.2. Maybe there is regression in 1.7.x branch (can't try 1.6.x branch cause I need to rebuild whole X for it, but if we need it it's possible).
Comment 5 Martin Flöser 2010-03-09 09:37:20 UTC
and you are using desktop effects?
Comment 6 Alexey Chernov 2010-03-09 09:39:53 UTC
No, there's no OpenGL support for my card so it's impossible to enable them (check drops on clicking Apply).
Comment 7 Martin Flöser 2010-03-09 09:48:55 UTC
In that case really a driver issue as kwin does not handle window painting if compositing is disabled. Sorry
Comment 8 Alexey Chernov 2010-03-09 09:54:54 UTC
Ok. Could you suggest, it's exactly driver problem or could be another part of X (maybe, Xserver)?
Comment 9 Martin Flöser 2010-03-09 10:03:08 UTC
My fair guess is, that it is a driver issue. As you mentioned it does not support OpenGL, so we have to consider that driver as unfinished ;-) But as I do neither have your graphics card, nor your system I can only guess.
Comment 10 Alexey Chernov 2010-03-09 10:11:07 UTC
Thank you, Martin. Will try to fix it)
Comment 11 Thomas Lübking 2010-03-09 15:55:19 UTC
as and _iff_ you don't use compositing at all, you should first extend /etc/X11/xorg.conf by

Section "Extensions"
        Option  "Composite" "Disable"
EndSection

in case that doesn't help, add
Option "XaaNoOffscreenPixmaps" "true"
tothe Screen section (this is not exactly a performance push, so disable it on no success)

and while i've no idea whether the driver supports it at all, you probably want
Option "BackingStore" "True"
in the device section w/o compositing
Comment 12 Alexey Chernov 2010-03-10 08:21:40 UTC
Thomas, thanks for your advice, I've added everything you've mentioned and bug luckily seems to go away. But performance is just horrible. You've written it could be because of XaaNoOffscreenPixmaps option, will try to switch it off. But anyway, we know, it's definitely a driver problem. Thank you.