Bug 362788 - Artifacts in the logout effect using amdgpu driver and opengl renderer
Summary: Artifacts in the logout effect using amdgpu driver and opengl renderer
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL: http://imgur.com/a/zcAzO
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-07 18:11 UTC by Luca Mastromatteo
Modified: 2016-06-04 14:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot "shadowboxes" (365.24 KB, image/png)
2016-05-09 19:59 UTC, FabiB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Mastromatteo 2016-05-07 18:11:32 UTC
I've got two archlinux running on two different pcs, one running with an AMD R9 380 using the amdgpu driver, and the other one running an integrated skylake iGPU. 
Basically, i've got artifacts when I push the logout button to exit my session, this does not happen into the other PC running the intel iGPU.
The great thing is that this problem seems to occur only with the OpenGL Renderer, and not with the XRender one. 
I was able to take some screenshots.

Reproducible: Always

Steps to Reproduce:
1. Press the logout button using the openGL renderer
2. Have a video card with the AMDGPU driver
3.

Actual Results:  
The fade animation has artifacts.

Expected Results:  
The animation should be normal
Comment 1 Thomas Lübking 2016-05-07 18:44:16 UTC
Smells like the blur shader being the ultimate trigger.

Could you add/override

[Effect-Logout]
UseBlur=false

in ~/.config/kwinrc

I'm *dead* sure we just had this, but cannot find the other bug.
The bug is probably in the driver, you could check dmesg and/or kwin's debug output for GL errors/warnings.

Can you please attach the output of "qdbus org.kde.KWin /KWin supportInformation"?
Comment 2 Luca Mastromatteo 2016-05-07 19:23:51 UTC
Nothing interesting from the dmesg. 
And yes, it seems to be the blur effect, no artifacts after disabling it. 
I didn't know where to put this since I didn't had problems with this driver since I've encountered in this.

Output of the command https://paste.kde.org/pg6yqrbf9

Running kwin from the terminal, with and without the option enabled in kwinrc didn't changed anything.

QXcbConnection: XCB error: 3 (BadWindow), sequence: 176, resource id: 10485766, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1531, resource id: 88080425, major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:                   X.Org
OpenGL renderer string:                 Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.7.1)
OpenGL version string:                  4.1 (Core Profile) Mesa 11.2.1
OpenGL shading language version string: 4.10
Driver:                                 Unknown
GPU class:                              Unknown
OpenGL version:                         4.1
GLSL version:                           4.10
Mesa version:                           11.2.1
X server version:                       1.18.3
Linux kernel version:                   4.5.2
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1753, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1754, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1755, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1756, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1757, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1758, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1759, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1760, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1763, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1764, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1765, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1766, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1767, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1768, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1769, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1770, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QMetaProperty::read: Unable to handle unregistered datatype 'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'
Comment 3 FabiB 2016-05-09 18:50:22 UTC
i can confirm this with AMD R9 380 and R9 Nano. Both with AMDGPU.
its not only the logout dialog but also window shadow drawings after a heavy openGL game. then there are no shadows anymore but artifact "blocks" or boxes
Comment 4 FabiB 2016-05-09 19:59:10 UTC
Created attachment 98868 [details]
screenshot "shadowboxes"
Comment 5 Thomas Lübking 2016-05-10 05:37:53 UTC
that's completely unrelated bug #361154, please atttach yourself there.
Comment 6 Martin Flöser 2016-05-11 07:51:44 UTC
setting to upstream as clearly driver bug
Comment 7 FabiB 2016-06-04 14:17:33 UTC
https://bugs.freedesktop.org/show_bug.cgi?id=94860 upstream bugreport (with workaround)