https://bugs.kde.org/show_bug.cgi?id=362137
Thomas Lübking <thomas.luebk...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking <thomas.luebk...@gmail.com> --- Well, now that the deliberate global QScreen crasher is gone, it can no longer stash the defects in QtQuick... => Upstream, compare bug #361439 or rather bug #361774 which is even more similar. Unfortunately we don't have debug values, but I guess that QOpenGLContext is dangeling/null in (rather than the dptr or it's screen member) since that's why QScreen was broken itfp... and to a certain degree we're likely just back on QTBUG-39996. The problem (here) would be that a signal causes ::setScreen on a dying GL context which largely seems to be the one of the QtQuick scene. Possibe QtQuick users in KWin (core) are - tabboxes except coverflow/slipswitch - the virtual desktop indicator - the buttons in presentwindows (close) and desktopgrid (+/-) effects - all aurorae driven decorations - things i might have forgotten. -- You are receiving this mail because: You are watching all bug changes.