SUMMARY Dolphin started crashing when acessing smb shares, right after entering the credentials. This started after the 25 versions. On version 24.12.3 it still works as it should STEPS TO REPRODUCE 1. open a smb share in dolphin 2. enter credentials OBSERVED RESULT crash EXPECTED RESULT acessing smb share SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION this is what I see when running dolphin with gdb: ... [Thread 0x7fff937fe6c0 (LWP 119866) exited] [Detaching after vfork from child process 120227] [Detaching after vfork from child process 120229] kf.kio.core: Internal error: itemsInUse did not contain QUrl("smb://myuser@mynas/") kf.kio.core: Fatal Error: HUH? Lister KDirLister(0x555555f92e20) is supposed to be listing, but has no job! Thread 1 "dolphin" received signal SIGABRT, Aborted. 0x00007ffff52dfcfc in ?? () from /usr/lib64/libc.so.6
Thanks for the bug report. Unfortunately there isn't enough information for us to try to figure out what's happening. Please add information about your system as requested in the bug report template. Copy and paste this with the information into a new comment. SOFTWARE/OS VERSIONS KDE Plasma Version: KDE Frameworks Version: Qt Version: Also, as the message at the top of the summary says, 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.
.
🐛🧹 ⚠️ 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!
Fixed in 25.04.3