[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-06-04 Thread FabiB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

--- Comment #7 from FabiB  ---
https://bugs.freedesktop.org/show_bug.cgi?id=94860 upstream bugreport (with
workaround)

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-11 Thread Martin Gräßlin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Martin Gräßlin  ---
setting to upstream as clearly driver bug

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

--- Comment #5 from Thomas Lübking  ---
that's completely unrelated bug #361154, please atttach yourself there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-09 Thread FabiB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

--- Comment #4 from FabiB  ---
Created attachment 98868
  --> https://bugs.kde.org/attachment.cgi?id=98868=edit
screenshot "shadowboxes"

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-09 Thread FabiB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

FabiB  changed:

   What|Removed |Added

 CC||plusf...@gmail.com

--- Comment #3 from FabiB  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-07 Thread Luca Mastromatteo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

--- Comment #2 from Luca Mastromatteo  ---
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'

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

2016-05-07 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362788

Thomas Lübking  changed:

   What|Removed |Added

  Component|scene-opengl|effects-various

--- Comment #1 from Thomas Lübking  ---
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"?

-- 
You are receiving this mail because:
You are watching all bug changes.