https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #6 from yktoo <ykt...@gmail.com> --- Also, I see that in your case it's some secondary thread that causes the SIGSEGV, for me it was the thread 1. So it's seemingly a different problem. -- You are receiving this mail because: You are watching all bug changes.
