Summary: | Dolphin crashing when dragging a file over the folder path location | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | James Beddek <telans> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | akselmo, itcramspam, kfm-devel |
Priority: | NOR | Keywords: | drkonqi |
Version: | 22.08.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
James Beddek
2022-10-14 01:06:10 UTC
I can no longer reproduce this with kdesrc-build. It was reproducible for me yesterday, but no longer since I've updated the sources. I've attempted to bisect any changes which may have had an impact on this with no luck (dolphin, plasma-framework, kwidgetsaddons, etc). Although it's no longer crashing, the terminal is spammed with "QCoreApplication::postEvent: Unexpected null receiver" while attempting to replicate the crash. This is still reproducible with release tarballs. I'm looking for guidance here now that I cannot reproduce on master - should this bug be closed or updated to reflect the postEvent spam? Created attachment 153017 [details]
New crash information added by DrKonqi
dolphin (22.08.1) using Qt 5.15.6
Dragging any file or folder into the folder path location bar in Dolphin results in a crash every time.
-- Backtrace (Reduced):
#4 0x00007fe245107906 in KDEPrivate::KUrlNavigatorButton::dragMoveEvent(QDragMoveEvent*) () from /lib64/libKF5KIOFileWidgets.so.5
#5 0x00007fe243cfb621 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#6 0x00007fe243dbecae in QAbstractButton::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#7 0x00007fe243e8c52c in QPushButton::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#8 0x00007fe243cbba40 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
*** This bug has been marked as a duplicate of bug 471279 *** |