Bug 352427 - EGL compositing problems, update only every other bookmark item in Chrome and Launcher
Summary: EGL compositing problems, update only every other bookmark item in Chrome and...
Status: RESOLVED DUPLICATE of bug 338150
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.3.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-08 07:58 UTC by Martin van Es
Modified: 2021-07-24 00:32 UTC (History)
2 users (show)

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


Attachments
Video demonstrating the bug (235.65 KB, video/mp4)
2015-09-08 08:09 UTC, Martin van Es
Details
Out of qdbus org.kde.KWin /KWin supportInformation (5.40 KB, text/plain)
2015-11-30 15:45 UTC, kamesh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin van Es 2015-09-08 07:58:11 UTC
As requested in bug #338434 I open this new one because it seems different from what caused those problems.

The symptoms are the same however: when using EGL, Chrome bookmarks menu highlight skips every other item, the same in Launcher. Switching to GLX fixes the problem.

GLStrictBinding=true and "None", or "full-screen repaints" don't solve the problem.

Reproducible: Always

Steps to Reproduce:
1. Use EGL for compositing
2. Open Chrome or Launcher
3. Browser through bookmarks menu or applications

Actual Results:  
Every other bookmark/application item is highlighted

Expected Results:  
Every item highlighted
Comment 1 Martin van Es 2015-09-08 08:09:02 UTC
Created attachment 94468 [details]
Video demonstrating the bug
Comment 2 Thomas Lübking 2015-09-08 08:18:59 UTC
Just to be absolutely sure: "None", or "full-screen repaints" are *NOT* values for GLStrictBinding but available settings in "kcmshell5 kwincompositing"
Comment 3 Martin van Es 2015-09-08 08:21:55 UTC
I know, I changed them using "System Settings" -> "Display and Monitor" -> "Compositor" -> apply but didn't do a restart (is that necessary?)
Comment 4 Thomas Lübking 2015-09-08 08:25:07 UTC
No, a restart isn't required (just wanted to be extra sure because of the reading of the line in the report, thanks for the video, btw.)
Comment 5 Martin Kostolný 2015-11-10 09:42:09 UTC
I can reproduce this issue with intel graphics. But enabling DRI3 (in xorg conf) solved this issue for me.

I think this bug should be marked as duplicate of this one: https://bugs.kde.org/show_bug.cgi?id=338150
Comment 6 Martin van Es 2015-11-10 09:53:53 UTC
Yes! Enabling DRI3 fixes my problems! I now can use EGL and see normal screen updates on Chrome bookmarks and launcher!
Comment 7 Thomas Lübking 2015-11-10 19:43:50 UTC

*** This bug has been marked as a duplicate of bug 338150 ***
Comment 8 kamesh 2015-11-29 01:52:24 UTC
I am using Kubuntu 14.04 LTS. I am having the exact same problem in Chrome, Vivaldi and Opera browsers. Firefox and launcher work fine though. I have an integrated graphics card from Intel. But, do not know how to enable DRI3. Can any one let me know?
Comment 9 Thomas Lübking 2015-11-29 07:16:39 UTC
/etc/X11/xorg.conf.d/20-intel.conf (or alter an existing configlet)
-------------------

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "DRI"    "3"
EndSection
Comment 10 kamesh 2015-11-29 21:19:30 UTC
I do not seem to have the folder "xorg.conf.d" in "/etc/X11". But, I have that folder in "/usr/share/X11/". That directory does not have the intel configuration file. So, I created a file called "20-intel.conf" under that directory and added the text you mentioned. 

user@Machine:/usr/share/X11/xorg.conf.d|
⇒  ls
10-evdev.conf   11-evdev-quirks.conf      20-intel.conf      50-vmmouse.conf  51-synaptics-quirks.conf
10-quirks.conf  11-evdev-trackpoint.conf  50-synaptics.conf  50-wacom.conf

But, it does not seem to solve the issue. I have made a video of my problem which can be found in the following link. Sometimes the issue is with menu listings and sometimes with bookmarks. But only on Chromium, Opera and Vivaldi browsers. Am I doing this right??

https://www.youtube.com/watch?v=9C_4_keUnSo
Comment 11 Thomas Lübking 2015-11-29 22:17:16 UTC
You can check /var/log/Xorg.0.log on the DRI version, notice that a restart of the X11 server is mandatory to apply changes, though usually logging out & back in would do that.

Please create /etc/X11/xorg.conf.d/ and put the file there, /usr/share/X11/xorg.conf.d/ is distro territory (ie. both paths are considered, but you're not supposed to use the /usr/share one yourself)
Comment 12 kamesh 2015-11-30 10:29:17 UTC
Now created /etc/X11/xorg.conf.d/ and kept the file there. Removed it from /usr/share/X11/xorg.conf.d/. Checked my Xorg.0.log. Link below. It shows reference to DRI 3. The problem is still not solved. There seems to be references to DRI 2 in my xorg.0.log file. I am not sure how to discern it. 

http://pastebin.com/cdDEgS80
Comment 13 kamesh 2015-11-30 10:32:45 UTC
Forgot to mention that I did a restart and checked my xorg.0.log file.
Comment 14 Thomas Lübking 2015-11-30 13:40:42 UTC
DRI3 is enabled (unless you disabled it at runtime, check "env | grep LIBGL_DRI3_DISABLE")

Please attach the output of "qdbus org.kde.KWin /KWin supportInformation"
Comment 15 Martin Kostolný 2015-11-30 14:08:52 UTC
I don't think the DRI3 module is loaded in your xorg. Here is how my log looks like when DRI3 is enabled (relevant part of the log):
http://pastebin.com/6rxYgG0r

But your xorg-server did find the Option "DRI" "3" as stated in your log so my guess is your xorg-server is built without DRI3 support. But there is a big chance I'm wrong...
Comment 16 Thomas Lübking 2015-11-30 14:13:54 UTC
(In reply to Martin Kostolný from comment #15)
> But there is a big chance I'm wrong...
Maybe, but you're right here. Sorry.
(shall teach me to no look too brief "dri2 and dri3 mentioned, option found, no error -> fine"...)

That's likely because of "14.04 LTS"
Comment 17 kamesh 2015-11-30 15:45:47 UTC
Created attachment 95817 [details]
Out of qdbus org.kde.KWin /KWin supportInformation

This is requested for the problem pertaining to the user Kamesh.
Comment 18 kamesh 2015-11-30 15:49:24 UTC
I do not get any output by running this command "env | grep LIBGL_DRI3_DISABLE". Output of "qdbus org.kde.KWin /KWin supportInformation" is attached. I did not change any runtime options. I mean I did not disable DRI3 module at runtime.

So, is it confirmed that my xorg-server is not compiled with DRI3 support? If yes, then what are the options for me and many other users using Kubuntu 14.04 LTS?
Comment 19 Thomas Lübking 2015-11-30 16:14:34 UTC
Debug out says that you're on KWin 4.11, you'd have to explicitly "export KWIN_OPENGL_INTERFACE="egl"" to use EGL itfp.

=> You don't run into this bug at all but rather bug #336589

run
   kwriteconfig --file kwinrc --group Compositing --key GLStrictBinding true

Also consider switching back to the raster graphicssystem.
Comment 20 kamesh 2015-12-01 12:06:54 UTC
Thank you Thomas. The kwriteconfig command worked and now the issue is resolved for me.

I guess the "export KWIN_OPENGL_INTERFACE="egl"" is not persistent across reboots but the issue seems to be resolved without it.
Comment 21 Thomas Lübking 2015-12-01 13:35:35 UTC
(In reply to kamesh from comment #20)

> I guess the "export KWIN_OPENGL_INTERFACE="egl"" is not persistent across
> reboots but the issue seems to be resolved without it.

No, but you probably don't want to use EGL anyway (you may try, but it'll hardly gain you performance advantages and rather cause more trouble on older drivers)
Comment 22 Martin van Es 2015-12-01 14:46:09 UTC
Apart from being the solution to my original problem (alternating highlights in KDE menu) I thought EGL was the future of accelerated compositing?
Comment 23 Thomas Lübking 2015-12-01 14:58:33 UTC
EGL is an X11 agnositic GLX (minus some cruft), ie. it's a platformless platform API, the future de toujours of OpenGL is Vulkan ;-)

The future of compositing is wayland (where we don't redirect windows into pixmaps, convert those to textures and paint that on screen, but paint the textures on screen that the clients paint into =)