https://bugs.kde.org/show_bug.cgi?id=357085
--- Comment #20 from Lorenzo Desole ---
Any news on this? Does anybody know if QT 5.6 solves it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357085
--- Comment #18 from Lorenzo Desole ---
I am assuming this won't be fixed prior to QT 5.6.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357085
--- Comment #12 from Lorenzo Desole ---
(In reply to Martin Klapetek from comment #11)
> Ok, good to know.
Here's a crash report with QT 5.5 (debug symbols included)
Thread 8 (Thread 0x7f36acea2700 (LWP 1703)):
#0
https://bugs.kde.org/show_bug.cgi?id=357085
--- Comment #10 from Lorenzo Desole ---
(In reply to Martin Klapetek from comment #9)
> > it would be very important to get a fix that hardens against this ASAP…
>
> If you're not running Qt 5.5.x, please upgrade ASAP. It will
https://bugs.kde.org/show_bug.cgi?id=357085
--- Comment #5 from Lorenzo Desole ---
I can confirm comment #3.
Crash report attached.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357085
Lorenzo Desole changed:
What|Removed |Added
CC|