http://bugzilla.opensuse.org/show_bug.cgi?id=967538
http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c21
--- Comment #21 from Wolfgang Bauer
That is, on a machine with Leap he does not have this problem?
I don't think he uses Leap...
Or does it indicate that this is not a KDE but (partially) a downstream problem?
No, it might still be a KDE problem, or it might also be an *upstream* problem (Qt). It just means he wasn't able yet to reproduce the crash, not more, not less. Makes it at least harder to fix for him though...
In other words: as I can trigger and reproduce it "on command", is there anything I could provide to further help to find the problem?
I can reproduce it reliably, on command, as well. And a backtrace has been attached to https://bugs.kde.org/show_bug.cgi?id=357413 too. The reporter of https://bugs.kde.org/show_bug.cgi?id=356945 apparently doesn't have any crashes, though. But the crash seems to be somewhere inside QtQuick, there are similar crash reports for other KDE components from what I have seen. It *might* even be specific to the Qt version, would explain why we can reliably reproduce it, but others can't... Of course I/we will try to resolve this as well. I just wanted to note that that particular statement was only about "New Session" not working, not the crash. And the two don't seem to be related (i.e. the fix for "New Session" will probably *not* fix the crash), as the crash also happens here when the screen locker is turned off. -- You are receiving this mail because: You are on the CC list for the bug.