Bug 512018 - Dolphin crash when accessing SMB share
Summary: Dolphin crash when accessing SMB share
Status: RESOLVED DUPLICATE of bug 507185
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.2
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-11-13 02:43 UTC by gaspump
Modified: 2025-11-13 23:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/294346/events/0de9f339f00241f393111aa1c164a839/


Attachments
New crash information added by DrKonqi (106.28 KB, text/plain)
2025-11-13 02:43 UTC, gaspump
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gaspump 2025-11-13 02:43:05 UTC
Application: dolphin (25.08.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.3
Frameworks Version: 6.19.0
Operating System: Linux 6.17.7-200.nobara.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: Nobara Linux 42 (KDE Plasma Desktop Edition)
DrKonqi: 6.5.2 [CoredumpBackend]

-- Information about the crash:
There was nothing particularly interesting about what was happening. I have some shares on a Windows 11 PC and have found some drawbacks to mounting these with fstab, so I thought I'd give Dolphin's "Network" sidebar another try despite never having much luck with it before (though it didn't crash, at least). I have no wacky Dolphin customization, mostly out-of-the-box save adjusting some of the icon sizes.

Steps to repro:
-I clicked Network > Shared Folders (SMB) > double clicked my Windows PC once it showed up
-When prompted I entered the credentials for the appropriate Windows user account
-On clicking OK or hitting enter Dolphin immediately crashes

This is reproducible every time for me. I don't see my distro in the dropdown here in the crash reporter but it's Nobara so probably from Fedora's repo.

I probably won't be able to help with any followup as, funnily enough, I'm about to wipe that Windows PC as the last step of fully moving to Linux and getting away from the malware Windows has become. But I figure if there's any other similar reports I could at least contribute the crash dump.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f69c9b9559a in QArrayDataPointer<KFileItem>::data (this=<optimized out>, this=<optimized out>) at /usr/include/qt6/QtCore/qarraydatapointer.h:120
#6  QArrayDataPointer<KFileItem>::constBegin (this=<optimized out>, this=<optimized out>) at /usr/include/qt6/QtCore/qarraydatapointer.h:126
#7  QList<KFileItem>::begin (this=<optimized out>, this=<optimized out>) at /usr/include/qt6/QtCore/qlist.h:659
#8  KCoreDirListerCache::slotUpdateResult (this=0x55c949a3bd90, j=<optimized out>) at /usr/src/debug/kf6-kio-6.19.1-1.fc42.x86_64/src/core/kcoredirlister.cpp:1731
#9  0x00007f69c73654ba in QtPrivate::QSlotObjectBase::call (this=0x55c94a093060, r=0x55c949a3bd90, a=0x7ffc6a008140) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#10 doActivate<false> (sender=0x55c94a165490, signal_index=6, argv=argv@entry=0x7ffc6a008140) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4170
[...]
#13 KJob::result (this=this@entry=0x55c94a165490, _t1=<optimized out>, _t1@entry=0x55c94a165490, _t2=...) at /usr/src/debug/kf6-kcoreaddons-6.19.0-1.fc42.x86_64/redhat-linux-build/src/lib/KF6CoreAddons_autogen/include/moc_kjob.cpp:475
#14 0x00007f69c93d74db in KJob::finishJob (this=0x55c94a165490, emitResult=<optimized out>) at /usr/src/debug/kf6-kcoreaddons-6.19.0-1.fc42.x86_64/src/lib/jobs/kjob.cpp:115
#15 0x00007f69c73654ba in QtPrivate::QSlotObjectBase::call (this=0x55c94a09e040, r=0x55c94a165490, a=0x7ffc6a008208) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#16 doActivate<false> (sender=0x55c94a161830, signal_index=7, argv=0x7ffc6a008208, argv@entry=0x0) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4170
[...]
#18 0x00007f69c9bb6a83 in KIO::WorkerInterface::finished (this=0x55c94a161830) at /usr/src/debug/kf6-kio-6.19.1-1.fc42.x86_64/redhat-linux-build/src/core/KF6KIOCore_autogen/include/moc_workerinterface_p.cpp:318
#19 KIO::WorkerInterface::dispatch (this=0x55c94a161830, _cmd=104, rawdata=...) at /usr/src/debug/kf6-kio-6.19.1-1.fc42.x86_64/src/core/workerinterface.cpp:125
#20 0x00007f69c9baeb55 in KIO::WorkerInterface::dispatch (this=0x55c94a161830) at /usr/src/debug/kf6-kio-6.19.1-1.fc42.x86_64/src/core/workerinterface.cpp:57
#21 0x00007f69c9bb18b0 in KIO::Worker::gotInput (this=0x55c94a161830) at /usr/src/debug/kf6-kio-6.19.1-1.fc42.x86_64/src/core/worker.cpp:262
#22 0x00007f69c73654ba in QtPrivate::QSlotObjectBase::call (this=0x55c94a147840, r=0x55c94a161830, a=0x7ffc6a0085a8) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#23 doActivate<false> (sender=0x55c94a145a60, signal_index=3, argv=0x7ffc6a0085a8) at /usr/src/debug/qt6-qtbase-6.9.3-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4170


Reported using DrKonqi
Comment 1 gaspump 2025-11-13 02:43:06 UTC
Created attachment 186743 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 TraceyC 2025-11-13 23:51:18 UTC
Thank you for the bug report. Based on the backtrace this looks like a duplicate of bug 507185. Please follow that report if you would like updates on the progress of this issue.

*** This bug has been marked as a duplicate of bug 507185 ***