I have Intel Haswell GPU and latest drivers from git (mesa, libdrm, xf86-video-intel). My problem here: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL version string: OpenGL ES 3.1 Mesa 13.1.0-devel (git-2e2562c) OpenGL shading language version string: OpenGL ES GLSL ES 3.10 Driver: Intel GPU class: Haswell OpenGL version: 3.1 GLSL version: 3.10 Mesa version: 13.1 X server version: 1.18.4 Linux kernel version: 4.8.6 Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(1, 0, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 0, 1, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.44882, 0.14882, 0.14882, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.50064, 0.80064, 0.50064, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.05054, 0.05054, 0.35054, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.3, 0, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 0.4, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 0, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.3, 0.4, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.134646, 0.044646, 0.044646, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.200256, 0.320256, 0.200256, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.02527, 0.02527, 0.17527, 0.6) Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0.360172, 0.390172, 0.420172, 0.6) kwin_core: ShaderManager self test failed kwin_core: Failed to initialize compositing, compositing disabled
It is seems like 367766 bug but for Intel.
why are you using OpenGL ES? Can you try using OpenGL and whether that also triggers the problem?
>why are you using OpenGL ES? Can you try using OpenGL and whether that also triggers the problem? Because some time in Gentoo I couldn't build kde without GLES2. Currently I can and I began to rebuild qt/kwin. I will write after this. PS or we can change engine by runtime?
> PS or we can change engine by runtime? Yes, but only the other way around. If built against OpenGL one can select OpenGL ES at runtime.
Thanks. After rebuild with -gles2 the effects have working. Hm... what break Intel again in OpenGL ES?!
Also now I see users icons on lockscreen.
great :-( let's see how it works at runtime: KWIN_COMPOSE=O2ES kwin_x11 --replace
>KWIN_COMPOSE=O2ES kwin_x11 --replace Same problem again. Pixel was QVector4D(0, 0, 0, 0.752941) expected QVector4D(0, 1, 0, 1) and etc
Ok, that's rather good. So it's not depending on compile time selection. That should help to tackle the issue. I guess that it might be a change with Mesa 13 - I should try to get it for my distro ;-)
(In reply to Martin Gräßlin from comment #9) > Ok, that's rather good. So it's not depending on compile time selection. > That should help to tackle the issue. > > I guess that it might be a change with Mesa 13 - I should try to get it for > my distro ;-) Gentoo really helpful for testing mainstream software. Also you can clone mesa and build by hands. I do it time to time for experiments. If you need any test or changes in kwin/mesa codes I can help.
yeah I know that one can easily build mesa.
*** This bug has been marked as a duplicate of bug 376801 ***
This is not a duplicate. This bug is reported against mesa 13 while the other is reported against mesa 17. The workaround proposed for mesa 17 would not work here.
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!