Brief description of system: Old but still kickin’:
–ASRock Z77 Extreme4 motherboard
–Intel Ivy Bridge CPU (i5)
–16 GB RAM
–multiple hard drives and SSD’s
–Intel AX210 add-in card (6 GHz WiFi works, which is really cool and a reason I am exploring Fedora 42 as a replacement for Windows 10)
–Nvidia GTX 970 GPU
–a DVD-RW drive which powers up but doesn’t work, but I don’t use it anyway.
“Monitor” is a 65" Samsung 4k TV, connected via GPU HDMI port.
Immediately after install, every time I tried to access an SMB share on the local network (Windows-based NAS, basically) through Dolphin, I got as far as entering login credentials, then Dolphin crashed.
OK…
Installed Nvidia drivers (570.144). Same result.
Added option to boot into X11 desktop instead of Wayland, because I didn’t get the full Nvidia control panel under Wayland (a known bug apparently). Using X11/xorg desktop, nvidia-settings app works fully (Yay!) but Dolphin still crashes when trying to access an SMB share (boo!).
SMB access does kinda work in this way however: Zero problems accessing SMB shares and playing media over the network via Kodi.
I don’t know where to go from here. Is there a less-buggy, alternate file system explorer I can use? Is there a way to make Dolphin behave?
If I launch Dolphin from a terminal, I see the following message after it crashes (when trying to access an SMB share):
kf.kio.core: Internal error: itemsInUse did not contain QUrl("smb://SMBusername@windowsmachine.local/")
KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2
Segmentation fault (core dumped)
Note that “windowsmachine.local” refers to the LAN SMB share I was attempting to access (which is running on a Windows machine). similarly, “SMBusername” is the account I created on that machine for file sharing.
As for coredumpctl, I was able to find this detailed info regarding the last Dolphin crash (using “coredumpctl info” option):
PID: 3083 (dolphin)
UID: 1000 (my_username)
GID: 1000 (my_username)
Signal: 11 (SEGV)
Timestamp: Wed 2025-05-14 14:03:13 MDT (1min 49s ago)
Command Line: /usr/bin/dolphin
Executable: /usr/bin/dolphin
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2>
Unit: user@1000.service
User Unit: app-\x2fusr\x2fbin\x2fdolphin@bfa2cf479ea74af1bb55db7166a0b6c6.service
Slice: user-1000.slice
Owner UID: 1000 (my_username)
Boot ID: e32234a73dfa42cba9fd8b8004d5682a
Machine ID: adb71d6e039a4c1ea08558399c37953b
Hostname: HostnameRedacted
Storage: /var/lib/systemd/coredump/core.dolphin.1000.e32234a73dfa42cba9fd8b8004d5682a.>
Size on Disk: 5.1M
Package: dolphin/25.04.0-3.fc42
build-id: e4e62544c4356265d8a02ec8df2f71d562d221b6
Message: Process 3083 (dolphin) of user 1000 dumped core.
Module /usr/bin/dolphin from rpm dolphin-25.04.0-3.fc42.x86_64
Module kuriikwsfilter.so from rpm kf6-kio-6.13.0-2.fc42.x86_64
Module fixhosturifilter.so from rpm kf6-kio-6.13.0-2.fc42.x86_64
Module localdomainurifilter.so from rpm kf6-kio-6.13.0-2.fc42.x86_64
Module libkuriikwsfiltereng_private.so.6 from rpm kf6-kio-6.13.0-2.fc42.x86_64
Module kurisearchfilter.so from rpm kf6-kio-6.13.0-2.fc42.x86_64
Further note: Same crash happens if I manually enter SMB host info in the address bar of Dolphin (e.g. “smb://192.168.x.y” and then enter login info).
I have the exact same behavior, but a different error on a fresh install of Fedora 42.
From the shell when it crashes:
kellic@prometheus:~$ kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
-I was just on Fedora 41, latest updates, no issues getting to the share.
-I open dolphin.
-Go to smb://xxx.xxx.xxx.xxx, it prompts for creds, I submit them, and it crashes.
Currently working on reporting it in the problem reporting tool. It’s working on a backtrace right now. Just figured I’d post it to let people know this may not be a one off issue.