Application: kdevelop (5.4.40) (Compiled from sources) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.8-arch1-1 x86_64 Windowing system: Wayland Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: It doesn't really happen all the time, just quite often. see from other bg repots that it's possibly something upstream but it's definitely a problem for KDevelop' usage. The crash can be reproduced sometimes. -- Backtrace (Reduced): #8 0x00007ff965c3dd4c in qt_message_fatal (context=..., message=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:1894 #9 0x00007ff965c3ea0d in QMessageLogger::fatal (this=this@entry=0x7fff3f0b8b80, msg=msg@entry=0x7ff965f463a8 "ASSERT failure in %s: \"%s\", file %s, line %d") at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #10 0x00007ff965c37e6c in qt_assert_x (where=where@entry=0x7ff967285e50 "QWidget::mapTo(const QWidget *parent, const QPoint &pos)", what=what@entry=0x7ff967285e28 "parent must be in parent hierarchy", file=file@entry=0x7ff967285c08 "/home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp", line=line@entry=4063) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.h:90 #11 0x00007ff966e8d155 in QWidget::mapTo (this=this@entry=0x55e2a8fe5650, parent=0x55e2aa2565b0, pos=...) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:4069 #12 0x00007ff966e6bebe in QWidgetRepaintManager::flush (this=this@entry=0x55e2ad2a6690, widget=widget@entry=0x55e2a8fe5650, region=..., widgetTextures=0x0) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/tools/qpoint.h:122 The reporter indicates this bug may be a duplicate of or related to bug 414556. Possible duplicates by query: bug 415294, bug 414922, bug 414556, bug 413943, bug 411017. Reported using DrKonqi
https://bugreports.qt.io/browse/QTBUG-76588?
Unsure, I'm in 5.14 branch. I could try reverting the commit mentioned on the bug... I have no idea how to predictably reproduce it.
The commit is already reverted in 5.14. Also the test case from the bug report doesn't trigger on me.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!