Summary: | black artefacts in region of a window while resizing it | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Pavel <fe-pavel> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | CC: | miramax166, rosenrotttt |
Priority: | NOR | Flags: | thomas.luebking:
Catalyst+
|
Version: | 4.9.4 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
URL: | http://youtu.be/J0D4X45fgvo | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | A screen of a 'damaged' window |
Description
Pavel
2012-08-12 12:20:15 UTC
- Screenshot? - Compositor (OpenGL/XRender) dependent? - Changing graphicssystem of kwin or the applications? Created attachment 73119 [details]
A screen of a 'damaged' window
(In reply to comment #1) > - Screenshot? > - Compositor (OpenGL/XRender) dependent? > - Changing graphicssystem of kwin or the applications? 1. screenshot have been just added as an attachment 2. Yes. The bug is taking place when OpenGL is active and don't appear when XRender is used 3. Changing graphicssystem of kwin - in the System Settings "Qt graphics system" (appeared in KDE 4.9) - The artifacts are always inside the window? - Do you use a transparent UI style like oxygen-transparent, or QtCurve resp. Bespin with the enabled feature? - Do you use the blur effect? Does the problem remain when you deactivate it? (In reply to comment #4) > - The artifacts are always inside the window? > - Do you use a transparent UI style like oxygen-transparent, or QtCurve resp. Bespin with the enabled feature? > - Do you use the blur effect? Does the problem remain when you deactivate it? 1. Yep. 2. Yes. The problem appears when I use transparent styles of windows. I switched to some non-transparent styles and everything was OK. More than that the performance when resizing was much higher. 3. Blur effect doesn't effect and the problem remains when blur stays deactivated. which Catalyst driver are you using? Does the problem persist if you enforce direct rendering: KWIN_DIRECT_GL=1 kwin --replace & (In reply to comment #6) > which Catalyst driver are you using? 12.6 >Does the problem persist if you enforce direct rendering? No, the artifacts are gone after this command is activated place an executable script containig #!/bin/sh export KWIN_DIRECT_GL=1 into ~/.kde/env it's probably time to set fglrx to dri since they apparently introduCed it by breaking indirect rendering :-) This bug is still resolved "upstream" and that's unlikely gonna change. If at all better monitor bug #311835 I confirm this bug. Laptop Asus X53B(K53BR) Yes, and it's a bug in fglrx, ie. the driver. Thus be bug is resolved upstream. Complain to AMD, we can't fix the actual bug (but only activatre dri, what should happen for fglrx 8.973/8.98 and later - as reported by "aticonfig --get-pcs-key=LDC,ReleaseVersion") http://ati.cchtml.com/show_bug.cgi?id=675 Vote please does this now happen with enforcing direct rendering as well? (In reply to comment #13) > does this now happen with enforcing direct rendering as well? It still does. But the lugs appear only in such heavy program like Eclipse (In reply to comment #14) > It still does. But the lugs appear only in such heavy program like Eclipse Eclipse is not only "heavy" but pretty "special" (sigh) So the video on the other bug was taken w/ indirect rendering? |