[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-07-05 Thread Paul de Vrieze
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #18 from Paul de Vrieze  ---
@martin I am not sure about that configuration, but I believe that it was due
to attempts to use wayland as well. I will try to have a look tomorrow, but it
is one of those gentoo choice things. I hadn't realised that kwin was using es.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-07-05 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #17 from Martin Flöser  ---
@Paul: how come that you use OpenGL ES?

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-07-04 Thread Paul de Vrieze
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #16 from Paul de Vrieze  ---
Created attachment 106442
  --> https://bugs.kde.org/attachment.cgi?id=106442&action=edit
Debug info when running mesa 17

I've attached the support information. I made a before version as well, but the
only differences are kwin version (5.10.2 instead of 5.10.3) and the
mesa/opengl versions.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-30 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376801

Martin Flöser  changed:

   What|Removed |Added

   Version Fixed In||5.10.4
  Latest Commit||https://commits.kde.org/kwi
   ||n/43816119e9ec74df228b42163
   ||b087e51b7541884
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #15 from Martin Flöser  ---
Git commit 43816119e9ec74df228b42163b087e51b7541884 by Martin Flöser.
Committed on 01/07/2017 at 06:19.
Pushed by graesslin into branch 'Plasma/5.10'.

Skip Shader self test for Mesa >= 17

Summary:
We are getting reports about the shader self test failing in a false
positive way on Mesa 17. We already have such false positve results
for NVIDIA quadro and went with disabling the self test.

Most likely our self test has a problem or the rendering of the first
frame has a problem. But disabling compositing because our rendering of
the first frame is broken, is too much.

Let's better be pro user here and disable the shader self test till we
fixed the root problem.
FIXED-IN: 5.10.4

Test Plan: It compiles.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D6426

M  +4-0libkwineffects/kwinglutils.cpp

https://commits.kde.org/kwin/43816119e9ec74df228b42163b087e51b7541884

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-29 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=376801

Rex Dieter  changed:

   What|Removed |Added

 CC||[email protected]

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-29 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #14 from Martin Flöser  ---
> Yes, sure; you mean the patch you sent on comment #11?

Yes or with the one you already created.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-29 Thread Krzysztof Nowicki
https://bugs.kde.org/show_bug.cgi?id=376801

Krzysztof Nowicki  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #13 from Krzysztof Nowicki  ---
*** Bug 372430 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-29 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #12 from Fabio Coatti  ---
(In reply to Martin Flöser from comment #10)
> I'm tempted to just disable the shader self test, but let's first try a
> little bit.
> 
> Can you please provide the output of:
> qdbus org.kde.KWin /KWin supportInformation
> 
> when running the patched KWin?

Yes, sure; you mean the patch you sent on comment #11?

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


[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-28 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #11 from Martin Flöser  ---
Phab request to disable shader self test on mesa 17:
https://phabricator.kde.org/D6426

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-28 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #10 from Martin Flöser  ---
I'm tempted to just disable the shader self test, but let's first try a little
bit.

Can you please provide the output of:
qdbus org.kde.KWin /KWin supportInformation

when running the patched KWin?

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-06-27 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376801

Christoph Feck  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #9 from Christoph Feck  ---
*** Bug 381318 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-03-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #8 from Martin Gräßlin  ---
It is useful. I'm going to just remove the self check. We have it 
failing on Nvidia and no on Mesa. In both cases is just the self check 
failing. Thus I assume we do something wrong during the setup. But a 
broken self check doesn't help us.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-03-05 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #7 from Fabio Coatti  ---
the same behaviour is present in 5.9.3 Out of curiosity, I disabled the checks
made by kwin (by returning a fake "True" result) and nothing blew up, now I'm
running mesa 17 with kwin 5.9.3

This is not a really useful info to solve the issue, I guess, but at least
could mean that the issue is not a major one :)

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-03-05 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

Fabio Coatti  changed:

   What|Removed |Added

Version|5.9.2   |5.9.3

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-27 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #6 from Fabio Coatti  ---
I've played around a little bit, and the reason that causes compositing to be
switched off seems to be unexpected results from 
glReadnPixels(x, y, 1, 1, GL_RGBA, GL_UNSIGNED_BYTE, 4, data);

that appears in kwinglutils.cpp, line 594 or so:


static bool checkPixel(int x, int y, const QVector4D &expected, const char
*file, int line)
{   
uint8_t data[4];
glReadnPixels(x, y, 1, 1, GL_RGBA, GL_UNSIGNED_BYTE, 4, data);  

const QVector4D pixel{data[0] / 255.f, data[1] / 255.f, data[2] / 255.f,
data[3] / 255.f};   

if (fuzzyCompare(pixel, expected))  
return true;

QMessageLogger(file, line, nullptr).warning() << "Pixel was" << pixel <<
"expected" << expected; 
return false;   
} 

With mesa17, I get this:

(never mind the numbers after pixel2, it is my addition to the code for no real
purpose :) )

feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 1, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 1, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 1, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 1, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(1, 0, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 1, 0, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 0, 1, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(1, 1, 1, 1) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0.760784, 0, 0, 0)
expected QVector4D(0.44882, 0.14882, 0.14882, 1) pixel2 QVector4D(194, 0, 0, 0) 
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0.760784, 0, 0, 0)
expected QVector4D(0.50064, 0.80064, 0.50064, 1) pixel2 QVector4D(194, 0, 0, 0) 
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0.760784, 0, 0, 0)
expected QVector4D(0.05054, 0.05054, 0.35054, 1) pixel2 QVector4D(194, 0, 0, 0) 
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0.760784, 0, 0, 0)
expected QVector4D(1, 1, 1, 1) pixel2 QVector4D(194, 0, 0, 0)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.3, 0, 0, 0.6) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 0.4, 0, 0.6) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0, 0, 0.5, 0.6) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.3, 0.4, 0.5, 0.6) pixel2 QVector4D(0, 0, 0, 192)   
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.134646, 0.044646, 0.044646, 0.6) pixel2 QVector4D(0, 0, 0,
192) 
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.200256, 0.320256, 0.200256, 0.6) pixel2 QVector4D(0, 0, 0,
192) 
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.02527, 0.02527, 0.17527, 0.6) pixel2 QVector4D(0, 0, 0,
192)
feb 27 23:22:14 calvin kwin_x11[19991]: Pixel was QVector4D(0, 0, 0, 0.752941)
expected QVector4D(0.360172, 0.390172, 0.420172, 0.6) pixel2 QVector4D(0, 0, 0,
192) 
feb 27 23:22:14 calvin kwin_x11[19991]: kwin_core: ShaderManager self test
failed  
feb 27 23:22:14 calvin kwin_x11[19991]: kwin_core: Failed to initialize
compositing, compositing

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-22 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #5 from Martin Gräßlin  ---
> some suggestion on how to get more debug messages?

Unfortunately not. We have had the NVIDIA driver also break in the past for
Quadro (only Quadro) cards in the self test and we didn't find any way to
properly debug this.

A few ideas I have is to experiment with various settings. E.g. switch between
OpenGL 2 and 3 in the compositor settings. Try using OpenGL ES. Switch between
EGL and GLX. For the last things we only have env variables.
https://community.kde.org/KWin/Environment_Variables

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-22 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #4 from Martin Gräßlin  ---
> however I got this error message by setting KWIN_GL_DEBUG 1

unrelated, that's just a bug in the shader generator.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-22 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #3 from Fabio Coatti  ---
Likely; however I got this error message by setting KWIN_GL_DEBUG 1

libkwinglutils: Failed to compile vertex shader: 
"0:2(1): preprocessor error: #version must appear on the first line\n\x00"
libkwinglutils: Failed to link shader: 
"error: no shaders attached to the program\n\x00"
kwin_core: OpenGL 2 compositing setup failed
kwin_core: Failed to initialize compositing, compositing disabled

I tried also to set 
QT_LOGGING_RULES "*.debug=true"

but I'm not sure that this change has been picked up, some suggestion on how to
get more debug messages?

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-22 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #2 from Martin Gräßlin  ---
if it worked before it indicates a regression mesa.

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

[kwin] [Bug 376801] kwin disables compositing with mesa 17

2017-02-22 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=376801

--- Comment #1 from Fabio Coatti  ---
forgot to say: mesa 13.X works fine

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