Bug 503771

Summary: Dolphin crashes when using backslashes in SMB URLs (smb:\\) instead of proper forward slashes (smb://).
Product: [Applications] dolphin Reporter: niklaswp
Component: bars: locationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: dolphin-bugs-null, john.kizer
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description niklaswp 2025-05-04 18:11:09 UTC 
SUMMARY
Dolphin crashes when using backslashes in SMB URLs (smb:\\) instead of proper forward slashes (smb://).

STEPS TO REPRODUCE
Open Dolphin.

In the address bar, type: smb:\\192.168.42.100

Press Enter.

OBSERVED RESULT
Dolphin immediately crashes. When launched from a terminal, it shows:

arduino
Kopieren
Bearbeiten
org.kde.dolphin: could not find entry for charset= "Andere Kodierung ()"
EXPECTED RESULT
Dolphin should handle invalid SMB URL formats more gracefully.
It could either auto-correct \\ to //, or display a friendly error message instead of crashing.
This issue affects users familiar with Windows-style UNC paths.

SOFTWARE/OS VERSIONS
Operating System: Nobara Linux 42 (Fedora-based)
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-200.nobara.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D
Memory: 62.7 GiB RAM
Graphics: NVIDIA GeForce RTX 4060
Dolphin Version: [add dolphin --version output here, e.g. 23.08.5]

ADDITIONAL INFORMATION
The correct URL smb://192.168.42.100 works without issues.

The crash is reproducible every time smb:\\ is entered.

This is a minor parsing mistake with major usability consequences.

Improving input sanitation could prevent frustration, especially for users transitioning from Windows.
Comment 1 John Kizer 2025-05-09 05:09:14 UTC 
Hi - If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 2 Bug Janitor Service 2025-05-24 03:47:42 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-06-08 03:47:53 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.