CPU/memory/disk monitor plasma widget

Compositing should rather have no impact on that. At least all plasmoids on the desktop are composited inside plasma-desktop, only panel translucency may fail.

If you think you spot bugs, please report them, ideally alongside screenshots.
Things don't fix by themselves, you know

bcooksley wrote:Does KWin indicate why it is falling back to XRender?
Have you tried setting OpenGL as the "Compositing type" in System Settings > Desktop Effects > Advanced?

My broken GL problem was fixed by your suggestion. Thanks.

Same issue when upgrading from 4.11 to 4.11 on Ubuntu

Same issue when upgrading from 4.11 to 4.11 on Ubuntu

... I bet this is wrong in some way

Please elaborate on
a) what you upgraded to what
b) whether you're operating on a virtual machine
c) (if no VM) what kind of GPU you're using (amd, legacy?)

Just wanted to revisit this issue as it still has relevance. I did a clean install of Kubuntu 13.10 as a VMWare Guest the other day and found I still had to apply this workaround. Fortunately this thread is still around so I could remind myself what I did to work around the problem.

I had the same problem with Kubuntu 14.04 running as guest on VMWare 10.

Everytime I selected (any) OpenGL as "Compositing Type" on "Desktop Effects/Advanced", it would revert to XRender and warn me with "5 desktop effects could not be loaded". My installation was actually an upgrade from 12.04 that was working fine.

Running `WIN_COMPOSE=O2 kwin --graphicssystem raster --replace &` solved it immediately, I now have to make it permanent.

Can't this be fixed permanently on KDE ?

please post the output of "glxinfo" on the VMWare machine (in a "Code" block, it's much text)

Thank you mgraesslin - you are the man!!!

Your solution finally solved my issue getting OpenGL Desktop Effects working om OpenSuSE 13.1 VMware guest on Professional Version 6.0.4 (1887983)

I had gone the full gamut with installing all the dependencies and compiling the Mesa 3D driver from the instructions on the mesa3d.org site and other guides, and it did load vmwgfx properly but Desktop Effects that required OpenGL still wouldn't work. I suspected that maybe something about the driver was the issue, so I started from scratch and installed Mesa3D using the 1-Click direct install here:

http://software.opensuse.org/package/Mesa

It turns out that both installation methods produced the desired driver setup as evidenced by the glxinfo output below, but still no OpenGL Desktop Effects!

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE;
OpenGL version string: 2.1 Mesa 9.2.3
OpenGL shading language version string: 1.20
OpenGL extensions:

I came across this thread and now I know it was a Kwin configuration all along!

As another poster suggested, I added an executable shell script to setup the KWIN environment properly and placed it in ~/.kde4/Autostart with the following contents:

#!/bin/sh
KWIN_COMPOSE=O2 kwin --graphicssystem raster --replace &

That works like a charm, thanks again!

I faced the same problem with a fresh new installation of Kubuntu x64 14.04.1 on VMWare 10.
Running `KWIN_COMPOSE=O2 kwin --graphicssystem raster --replace &` solved it.

I have a similar problem on VirtualBox (I run Debian testing guest on Debian testing host). I set enable 3D accelration in VM settings, but it just fails to switch on direct rendering in X.org. The host system is using closed Nvidia driver if that makes any difference.

That workaround with putting these in .kde/env script:

export KWIN_DIRECT_GL=1
export KWIN_COMPOSE=O2

mentioned in the corresponding bug (https://www.virtualbox.org/ticket/4582) produces an unusable desktop for me.

I see this error in X.org log:

Code: Select all

[    16.424] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[    16.424] (II) The file referenced, is *NOT* loaded
[    16.424] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[    16.424] (EE) AIGLX error: vboxvideo does not export required DRI extension
[    16.424] (EE) AIGLX: reverting to software rendering
[    16.960] (II) AIGLX: Loaded and initialized swrast
[    16.960] (II) GLX: Initialized DRISWRAST GL provider for screen 0


Any idea what can be done about it, or it's a problem with VirtualBox?

Virtualbox uses the software rasterizer (ie. will be sloooooooooooooooow)

It's either an issue about the nvidia blob, or you got sth. like:

WARNING: The vboxdrv kernel module is not loaded.

and ignored it or the host/guest has no drivers installed (in particular not the nvidia blob)

Does the guest xorg.log have any reference to nvidia at all?

luebking wrote:Virtualbox uses the software rasterizer (ie. will be sloooooooooooooooow)

It's either an issue about the nvidia blob, or you got sth. like:

WARNING: The vboxdrv kernel module is not loaded.

and ignored it or the host/guest has no drivers installed (in particular not the nvidia blob)

Does the guest xorg.log have any reference to nvidia at all?

dmesg on the host system shows this:

Code: Select all

[   16.464654] vboxdrv: Found 8 processor cores.
[   16.464925] vboxdrv: fAsync=0 offMin=0x1e7 offMax=0x1f308
[   16.464970] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   16.464971] vboxdrv: Successfully loaded version 4.3.18_Debian (interface 0x001a0008).

/var/log/Xorg.0.log of the guest has no mention of Nvidia. Does guest require Nvidia blob installed inside itself? I thought it's using VirtualBox own video driver which communicates with the host system somehow. And that VB driver exposes OpenGL to the desktop. The host system has Nvidia blob installed for sure.

I tried it with guest additions installed from CD inside the guest, and with packages which are provided by Debian. Both produced same results.

> Does guest require Nvidia blob installed inside itself?
See eg. here - I doubt nvidia will work other than by pci passthrough.
http://askubuntu.com/questions/202926/h ... virtualbox

You could also check lspci in vbox to check what hardware is "emulated".