https://bugs.kde.org/show_bug.cgi?id=357728
--- Comment #12 from Bernd Steinhauser <li...@bernd-steinhauser.de> --- (In reply to Bernd Steinhauser from comment #11) > (In reply to Thomas Lübking from comment #10) > > > layers.acceleration.disabled false > > layers.acceleration.disabled true > This is the first thing I'm trying and so far it looks good, I haven't had a > freeze since. Will require some more time to be sure, though. Was wrong here. The day after I wrote this, I had a freeze with a completely unrelated non-gtk and non-Qt application. (It's actually a java one.) The acceleration in FF was disabled at the time. So this was not it. The next thing I tried was this: > > kwin4_effect_translucency > Try to disable this. I've disabled this since the 15th of January. I've been happily dragging windows around and I haven't seen a freeze since then. Since that was over 2 weeks ago, I think it's relatively safe to so that the issue was caused by the translucency effect. Of course this means that without the compositor enabled this should not happen and this > I think (but I'm not sure here), I've even tried with the compositor switched > off would have been wrong? Are there special OpenGL extensions that translucency requires? Maybe I could have a look at the kernel/mesa changes related to that and see if there were changes that could cause this kind of behavior? -- You are receiving this mail because: You are watching all bug changes.
