https://bugs.kde.org/show_bug.cgi?id=359177
--- Comment #12 from Martin Steigerwald <mar...@lichtvoll.de> --- Okay. On the same day I tested further around. It then also happened if one session is MATE and one is Plasma. But it didn´t happen if there was only one session and it is Plasma. So two Plasma sessions or two sessions one MATE (I think it doesn´t matter) one Plasma triggers it. It then came to my mind that I changed another setting that at first I didn´t relate to this: I found that in both sessions XRender was set as compositor. I didn´t think thats right for Intel Sandybridge graphics, so I set it to OpenGL 3.1 with GLX as I think I had it on both sessions for quite some time (I had issues with EGL I think I reported here as well). As I set compositing back to XRender I was able to use two Plasma sessions like before again. I also ruled out the kernel or whether KDE Frameworks + KDEPIM is self-compiled or from packages as it happened as well with 4.4 kernel + packaged Plasma / KDE Frameworks. I now have 4.5-rc3 kernel + self-compiled stuff again and two sessions still work. So whenever I run one Plasma session with OpenGL 3.1 on GLX compositing together with any other session at some times it makes kaboooom on switching between the sessions. If I use two Plasma session, it blanks only one of them. The other is still fine. I am not sure what to make of this. I am willing to close this bug report and start a new one if it got to confusing. Please advice. -- You are receiving this mail because: You are watching all bug changes.
