(In reply to comment #197) > It *is* disabled by default - what does not prevent people from happily > activating it, because some guy in a random forum told them "it's the best > trick ever" - and then report crashes in driver that resolve by "after > disabling unredirection, bug is gone" Then add big red label in KCM: "This could cause crashes. Don't file bugs, you've been warned". Compositing could also cause problems with buggy drivers.
> We basically (and actually for far too long) expose users to a feature, > while knowing it will crash their WM more or less for sure. For me it NEVER crashed KWin or anything. > > It worked for me very well (Intel HD 3000). > Since you mentioned DRI_PRIME, it will rather be some IGP-GPU briged system? Yes, but KWin is always running on Intel, and doesn't even know about Radeon. > As far as i was told, DRI_PRIME does only work *with* redirection, ie. > whenever you disable the compositor, the DRI_PRIME context paints nothing. No, for me it paints black screen when compositing is enabled (without unredirection). > If it does NOT work redirected for you, the better solution to suspend > compositing altogether is not affected. I can't find an option to automatically suspend compositing in KCM. Instead there's now non-working (silently!) option for unredirection. And... Mutter and Compiz now do unredirection by default. And seems that they don't crash too much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs