https://bugs.kde.org/show_bug.cgi?id=364433
--- Comment #4 from Sven Brauch <m...@svenbrauch.de> --- I can reproduce this as well, and I see it with Python too. The backtrace with the new assistant is different: Thread 1 (Thread 0x7f1393626800 (LWP 4533)): [KCrash Handler] #5 0x00007f138c8928e0 in typeinfo name for QObjectPrivate () from /usr/lib/libQt5Core.so.5 #6 0x00007f13936267f0 in ?? () #7 0x00007f138d5bc9ec in QTextEdit::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x00007f138d460f18 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x00007f138d54862e in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #10 0x00007f138c7399e1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #11 0x00007f138d419e15 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x00007f138d42246d in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x00007f138c739c80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x00007f138d420b1d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/libQt5Widgets.so.5 #15 0x00007f138d47afc0 in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x00007f138d47d763 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x00007f138d419e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x00007f138d4215b1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x00007f138c739c80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x00007f138cc880e3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #21 0x00007f138cc89c65 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #22 0x00007f138cc67cbb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5 #23 0x00007f1374847310 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #24 0x00007f1380489dd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x00007f138048a040 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0x00007f138048a0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x00007f138c78e57f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #28 0x00007f138c7380da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #29 0x00007f138c7405cc in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #30 0x000000000040df15 in main (argc=1, argv=0x7ffec2acccd8) at ../app/main.cpp:759 I have no idea what is going on here. It's some kind of memory corruption, but I really don't know where it comes from or why it happens. QTextEdit is always in the backtrace for some reason. -- You are receiving this mail because: You are watching all bug changes.
