Dolphin isn't able to reach the shared Windows directory (error occurred).
Dolphin isn't able to reach the shared Windows directory (error occurred).
Previously I relied on W11 on PC "A" as a backup for PC "B". We shared read access to a single folder on B, and from A I manually backed it up using free file sync. This process functions perfectly on a few W11 machines. On A I now run Fedora 42 with KDE Dolphin, which uses the Dolphin file manager. Initially, I could access the folder on B and view all files without issues. Recently, however, I still see B but clicking the folder causes Dolphin to crash with minimal feedback. Free File sync also can't reach those folders anymore. I'm currently on another W11 PC and can access the shared folder fine. I've learned that Samba needs to be installed, and a "Dolphin - Samba Filesharing Plugin" is already present. I'm unsure how to modify it if needed. Dolphin lacks settings for this, so what else should I try? Since it worked before, I suspect this might be a coincidence, but restarting didn't help. An unusual observation is that originally I had to enter PC B's credentials and there was an option to remember the password, similar to what W11 does. When I tried to log in, the window reappeared with credentials filled, but after confirming OK it crashed. I applied all available updates and restarted, but nothing resolved the issue. Should I adjust any settings or install additional software? Would reinstalling Dolphin be necessary without risking my operating system? I checked the Dolphin add-ins, but only three were listed—graphics or video transfer weren't selected, possibly because the apply button didn't function when those were checked.
You might try reinstalling Dolphin, as it seems to be your top choice.
I reinstalled Dolphin again, but the issue persists. My login details are still saved. Edited August 22, 2025 by Needfuldoer
smb://[user]@[host]/[path]. Other protocols like nfs and fish are also viable, offering better performance if you can adjust your settings. Also verify that the cifs modules are loaded using lsmod|grep cifs; absence indicates you may need to consult the forums for more guidance.
Thanks. I will try that. But I'm also preparing myself to have to re-install the OS. But that also makes me question the choice of OS. I assumed Fedora is a good balance between stability and bleeding edge. Maybe too much bleeding? Since this is a feature that worked at first, but then stopped working. If i have to re-install anyway, should i rather get Debian 13 KDE? (this is an old i7 -7700k system with iGPU)
I’m not sure about this situation, as I haven’t done it much recently. @Ralphred’s advice seems the most reliable. Still, you might want to consider a few options. First, downgrade "kdenetwork-filesharing," the package that offers Samba integration with KDE, and check if it resolves the problem. Log out and back in after making this change. This bug might be linked to it, so it could fix the issue. If it does, pin the version to avoid automatic upgrades during future updates.
If samba is the culprit, you can try downgrading it as well. If neither works, there could be another cause. With Fedora updates, fixes usually spread quickly, though bugs can appear too. Generally, there’s a balance between staying current and maintaining stability—Debian with KDE should offer a similar experience, though it has a two-year release cycle focused mainly on bug fixes.
Reported issue detailing identical symptoms as @Lurking, identified as a cross-distro bug. Consider their fixes before my generic recommendations if possible!
I'm not the right person to ask about honesty because each system has its own strengths and weaknesses that need personal evaluation. The choice between Redhat, Debian, and Arch depends on individual preferences and priorities. Fedora offers a straightforward experience as it's essentially RHEL in beta, balancing stability, ease of use, and relevance. Arch provides cutting-edge features but can be complex due to its precompiled packages and mixed support for advanced users. Debian serves as a solid foundation, especially for those seeking more than what Alpine offers, though it requires some technical know-how. Overall, Debian remains my top suggestion for most users.
I highly suggest going with Fedora. Restoring the system is rarely required, and most problems stem from your personal user settings. A simple test works well: make a new account, log in as that user, and see if you can access the shared folder.