Bug 503902

Please share more of the trace.

You should be able to expand it or run: coredumpctl -1 debug dolphin --debugger-arguments="-ex bt"

(In reply to Méven from comment #1)
> Please share more of the trace.
> 
> You should be able to expand it or run: coredumpctl -1 debug dolphin
> --debugger-arguments="-ex bt"

After the crash, I rebooted into kernel 6.14.4-300.fc42.x86_64 which didn't have the issue, then back into 6.14.5-300.fc42.x86_64, where the issue disappeared, and now can't be replicated.

However, here is the trace:

#0  0x00007fde9e88111c __pthread_kill_implementation (libc.so.6 + 0x7311c)
#1  0x00007fde9e827afe raise (libc.so.6 + 0x19afe)
#2  0x00007fdea13adef1 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x4ef1)
#3  0x00007fde9e827c30 __restore_rt (libc.so.6 + 0x19c30)
#4  0x00007fde9e8876c0 __syscall_cancel_arch (libc.so.6 + 0x796c0)
#5  0x00007fde9e87b9da __internal_syscall_cancel (libc.so.6 + 0x6d9da)
#6  0x00007fde9e87c04c __futex_abstimed_wait_common (libc.so.6 + 0x6e04c)
#7  0x00007fde9e87e71e pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x7071e)
#8  0x00007fde9f0cbb2c _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2cbb2c)
#9  0x00007fdea08d3555 _ZN23QDBusPendingCallPrivate15waitForFinishedEv (libQt6DBus.so.6 + 0x7d555)
#10 0x00007fdea0b6753f _ZZN12KUrlMimeData18exportUrlsToPortalEP9QMimeDataENKUlvE0_clEv.lto_priv.0 (libKF6CoreAddons.so.6 + 0x5153f)
#11 0x00007fdea0b6f4f6 _ZN12KUrlMimeData18exportUrlsToPortalEP9QMimeData (libKF6CoreAddons.so.6 + 0x594f6)
#12 0x00007fdea19e669f _ZN19KItemListController13startDraggingEv (libdolphinprivate.so.6 + 0x6c69f)
#13 0x00007fdea19e72d2 _ZN19KItemListController14mouseMoveEventEP24QGraphicsSceneMouseEventRK10QTransform (libdolphinprivate.so.6 + 0x6d2d2)
#14 0x00007fdea19ed266 _ZN19KItemListController12processEventEP6QEventRK10QTransform (libdolphinprivate.so.6 + 0x73266)
#15 0x00007fdea19f5bd9 _ZN13KItemListView5eventEP6QEvent (libdolphinprivate.so.6 + 0x7bbd9)
#16 0x00007fdea003d7af _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x3d7af)
#17 0x00007fde9eef5fa8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0xf5fa8)
#18 0x00007fdea0474ba5 _ZN21QGraphicsScenePrivate9sendEventEP13QGraphicsItemP6QEvent (libQt6Widgets.so.6 + 0x474ba5)
#19 0x00007fdea0474ff9 _ZN21QGraphicsScenePrivate14sendMouseEventEP24QGraphicsSceneMouseEvent (libQt6Widgets.so.6 + 0x474ff9)
#20 0x00007fdea048567b _ZN14QGraphicsScene14mouseMoveEventEP24QGraphicsSceneMouseEvent (libQt6Widgets.so.6 + 0x48567b)
#21 0x00007fdea048da5c _ZN14QGraphicsScene5eventEP6QEvent (libQt6Widgets.so.6 + 0x48da5c)

(In reply to Paul from comment #2)
> (In reply to Méven from comment #1)
> > Please share more of the trace.
> > 
> > You should be able to expand it or run: coredumpctl -1 debug dolphin
> > --debugger-arguments="-ex bt"
> 
> After the crash, I rebooted into kernel 6.14.4-300.fc42.x86_64 which didn't
> have the issue, then back into 6.14.5-300.fc42.x86_64, where the issue
> disappeared, and now can't be replicated.
> 

The kernel update didn't do anything, but the reboot allowed to reload your libraries that could have mismatched versions in memory.
That's a very common way users can create trouble for themselves: not rebooting after upgrades (or at least logging out).

> However, here is the trace:
> 
> #0  0x00007fde9e88111c __pthread_kill_implementation (libc.so.6 + 0x7311c)
> #1  0x00007fde9e827afe raise (libc.so.6 + 0x19afe)
> #2  0x00007fdea13adef1 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 +
> 0x4ef1)
> #3  0x00007fde9e827c30 __restore_rt (libc.so.6 + 0x19c30)
> #4  0x00007fde9e8876c0 __syscall_cancel_arch (libc.so.6 + 0x796c0)
> #5  0x00007fde9e87b9da __internal_syscall_cancel (libc.so.6 + 0x6d9da)
> #6  0x00007fde9e87c04c __futex_abstimed_wait_common (libc.so.6 + 0x6e04c)
> #7  0x00007fde9e87e71e pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x7071e)
> #8  0x00007fde9f0cbb2c _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer
> (libQt6Core.so.6 + 0x2cbb2c)
> #9  0x00007fdea08d3555 _ZN23QDBusPendingCallPrivate15waitForFinishedEv
> (libQt6DBus.so.6 + 0x7d555)
> #10 0x00007fdea0b6753f
> _ZZN12KUrlMimeData18exportUrlsToPortalEP9QMimeDataENKUlvE0_clEv.lto_priv.0
> (libKF6CoreAddons.so.6 + 0x5153f)
> #11 0x00007fdea0b6f4f6 _ZN12KUrlMimeData18exportUrlsToPortalEP9QMimeData
> (libKF6CoreAddons.so.6 + 0x594f6)
> #12 0x00007fdea19e669f _ZN19KItemListController13startDraggingEv
> (libdolphinprivate.so.6 + 0x6c69f)

Thank you for the back trace still.

> The kernel update didn't do anything, but the reboot allowed to reload your
> libraries that could have mismatched versions in memory.
> That's a very common way users can create trouble for themselves: not
> rebooting after upgrades (or at least logging out).

Let me calrify. I did indeed reboot after kernel upgrade, but since it didn't work, I tried to boot into an older kernel which worked.
After that I once again tried the new kernel which then worked.

Update: 
I'm still having issues with drag and cut in Dolphin on 6.14.5-300.fc42.x86_64.
It sometimes causes the application to close silently with no coredump or crash dialog.

Log:
May 15 23:39:36 core dolphin[103005]: kf.coreaddons: Some files could not be exported.  QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
May 15 23:41:22 core systemd[2206]: app-org.kde.dolphin@e5c3d7f94c8f40b39df7f96307458a86.service: Consumed 11.196s CPU time, 303.3M memory peak, 16.1M memory swap peak.