[dolphin] [Bug 504906] New: Dolphin crashes when trying to connect to SMB fileshare.
Ser Drakström
bugzilla_noreply at kde.org
Wed May 28 12:05:14 BST 2025
https://bugs.kde.org/show_bug.cgi?id=504906
Bug ID: 504906
Summary: Dolphin crashes when trying to connect to SMB
fileshare.
Classification: Applications
Product: dolphin
Version First 25.04.1
Reported In:
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: huux at protonmail.com
CC: kfm-devel at kde.org
Target Milestone: ---
Created attachment 181822
--> https://bugs.kde.org/attachment.cgi?id=181822&action=edit
dolphin logs. crashing and working.
SUMMARY
Dolphin crashes when accessing an SMB share using an unsupported protocol.
After a few retries, it may not crash.
STEPS TO REPRODUCE
1. Open Dolphin
2. In the address bar, enter smb://192.168.1.x/
3. Enter login credentials when prompted
4. Press Enter
5. Dolphin crashes (note: may not happen every time)
OBSERVED RESULT
Dolphin crashes with a core dump. Terminal output includes:
smbXcli_negprot_smb1_done: No compatible protocol selected by server.
kf.kio.core: Internal error: itemsInUse did not contain
QUrl("smb://x@192.168.1.x/")
kf.kio.core: Fatal Error: HUH? Lister ... is supposed to be listing, but has no
job!
zsh: IOT instruction (core dumped) dolphin
EXPECTED RESULT
Dolphin should handle the error gracefully and show a clear message such as:
"No compatible SMB protocol found."
It should not crash.
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D
Memory: 31.3 GiB
Graphics Processor: NVIDIA GeForce RTX 4080
ADDITIONAL INFORMATION
The crash seems to be triggered by SMB protocol negotiation failure with the
server.
KIO does not appear to handle this edge case correctly, leading to a crash
rather than a fallback or error message.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list