https://bugs.kde.org/show_bug.cgi?id=456499

--- Comment #1 from Brennan Kinney <polarathene-sig...@hotmail.com> ---
I forgot to add that I did test with the official Breeze theme.

---

This bug may only affect VMware guests.

There is a related bug report from 2017 that describes this bug more briefly,
and later discovers a workaround via an ENV that drops OpenGL in the guest down
to 2.1:

https://bugs.kde.org/show_bug.cgi?id=376115#c4

> `export SVGA_VGPU10=0` anywhere so it would be applied to all 3D apps.

[Referencing Mesa SVGA3D driver
docs](https://docs.mesa3d.org/drivers/svga3d.html) (which seems a bit outdated
in content)

> OpenGL 3.3 support can be disabled by setting the environment variable 
> SVGA_VGPU10=0. You will then have OpenGL 2.1 support. This may be useful to 
> work around application bugs (such as incorrect use of the OpenGL 3.x core 
> profile).

---

Setting the ENV into the bash profile and restarting, the graphical failure is
no longer reproducible:

    $ echo "export SVGA_VGPU10=0" >> ~/.bashrc

Fedora 36 logs (journalctl -b0) after toggling the compositor on:

Jul 09 18:48:17 fedora kwin_x11[1304]: OpenGL vendor string:                  
VMware, Inc.
Jul 09 18:48:17 fedora kwin_x11[1304]: OpenGL renderer string:                
SVGA3D; build: RELEASE;  LLVM;
Jul 09 18:48:17 fedora kwin_x11[1304]: OpenGL version string:                 
2.1 Mesa 22.1.3
Jul 09 18:48:17 fedora kwin_x11[1304]: OpenGL shading language version string:
1.20
Jul 09 18:48:17 fedora kwin_x11[1304]: Driver:                                
VMware (SVGA3D)
Jul 09 18:48:17 fedora kwin_x11[1304]: GPU class:                             
Unknown
Jul 09 18:48:17 fedora kwin_x11[1304]: OpenGL version:                        
2.1
Jul 09 18:48:17 fedora kwin_x11[1304]: GLSL version:                          
1.20
Jul 09 18:48:17 fedora kwin_x11[1304]: Mesa version:                          
22.1.3
Jul 09 18:48:17 fedora kwin_x11[1304]: X server version:                      
1.20.14
Jul 09 18:48:17 fedora kwin_x11[1304]: Linux kernel version:                  
5.18.9
Jul 09 18:48:17 fedora kwin_x11[1304]: Requires strict binding:               
yes
Jul 09 18:48:17 fedora kwin_x11[1304]: GLSL shaders:                          
yes
Jul 09 18:48:17 fedora kwin_x11[1304]: Texture NPOT support:                  
yes
Jul 09 18:48:17 fedora kwin_x11[1304]: Virtual Machine:                       
yes
Jul 09 18:48:18 fedora kwin_x11[1304]: QObject::connect(KWin::InputMethod,
KWin::EffectsHandlerImpl): invalid nullptr parameter

---

It may still be considered a possible bug in the effect. But I am also aware of
Chrome based web browsers all having rendering issues unless switching to their
Vulkan experimental rendering backend (in chrome://flags), that workaround is
not required when OpenGL drivers are reset to 2.1.

The fix worked for both openSUSE Tumbleweed and Fedora 36, but NOT for
EndeavourOS. It is unclear why, but it may be a timing issue? 

`inxi -G` and `glxinfo | grep -i opengl` both report OpenGL 2.1, but kwin (X11
and Wayland) is started with OpenGL 4.1, requiring manual `kwin_x11 --replace
&` to be run to restart kwin when it will then also use OpenGL 2.1.

I have run without systemd startup for EndeavourOS:

    kwriteconfig5 --file startkderc --group General --key systemdBoot false
    qdbus org.kde.KWin /KWin supportInformation | grep -i opengl

This did not help and still required manually restarting kwin to switch OpenGL
used from 4.1 to 2.1. The ENV set in bashrc is perhaps applied too late for
this distro with kwin initializing earlier?

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

Reply via email to