https://bugs.kde.org/show_bug.cgi?id=383655
Emmanuel Lepage Vallée changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=383655
--- Comment #5 from Emmanuel Lepage Vallée ---
Umm, it might be another bug on your system. It's very strange/problematic
because the backtrace is totally inconclusive (as you already noticed).
On my system (still locked to Qt 5.7 as it is the minimum
https://bugs.kde.org/show_bug.cgi?id=383655
--- Comment #4 from nroycea+...@gmail.com ---
Curious, it says "Fix Version/s: 5.9.0 Alpha", but qtdiag shows
Qt 5.9.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC
7.1.1 20170630) on "xcb"
OS: Arch Linux [linux version 4.12.8-2-ARCH
https://bugs.kde.org/show_bug.cgi?id=383655
Emmanuel Lepage Vallée changed:
What|Removed |Added
Severity|crash |normal
--- Comment #3 from Emmanuel Le
https://bugs.kde.org/show_bug.cgi?id=383655
Christoph Feck changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=383655
--- Comment #2 from Emmanuel Lepage Vallée ---
s/Two of them/I fixed 2 of them/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383655
--- Comment #1 from Emmanuel Lepage Vallée ---
Two of them (at least, 2 crashes) and about 70 memory leaks have been fixed.
It's not to the point where it quits cleanly. Even after this, it probably wont
because that QBus connection use-after-free is in
