Bug 509295

Summary:	Dolphin displays "No shared folders found" for some valid SMB locations
Product:	[Applications] dolphin	Reporter:	clemens.brunner
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	dolphin-bugs-null, meven
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description clemens.brunner 2025-09-09 06:50:20 UTC

This is similar to https://bugs.kde.org/show_bug.cgi?id=509253, but also happens for non-empty folders.

SUMMARY
Dolphin displays "No shared folders found" for some valid SMB locations. I haven't figured out why this happens for some shares and not others, but I can reproduce it in my company network for at least two shares.

STEPS TO REPRODUCE
1. Enter a valid SMB share URI in the location bar and hit Enter
2. Enter username and password

OBSERVED RESULT
Dolphin displays "No shared folders found".

EXPECTED RESULT
Dolphin should display the contents of the share.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
I confirmed that the share exists and works with both smbclient as well as GNOME Files.

Comment 1 clemens.brunner 2025-10-15 11:23:22 UTC

I think it might be due to the fact that some parts of the path are hidden (i.e., where I don't have read access), e.g. assuming my share is located at `smb://some/path/to/folder`, but I do not have read access to the `to` folder. I'm not sure how to debug this issue though, any suggestions are welcome.

Comment 2 Méven 2025-10-15 15:39:21 UTC


*** This bug has been marked as a duplicate of bug 509253 ***

Comment 3 clemens.brunner 2025-10-20 13:11:34 UTC

I don't think that this is a duplicate of 509253, and the proposed fix also doesn't work for me.

When trying to access a subdirectory of a valid Samba share via Dolphin (e.g., smb://server/share/subdir/deepdir), the following error appears:

Internal Error - Unknown error condition: [11] Resource temporarily unavailable

The top-level share and its immediate subdirectory are accessible, but going one level deeper triggers the error. The same path works with GNOME Nautilus and smbclient (i.e., smbclient //server/share -U username; cd subdir/deepdir works). The server is part of an Active Directory domain and likely uses DFS. Dolphin seems to treat deep paths as new tree connects or mishandles DFC referrals.

Comment 4 Méven 2025-10-21 08:12:51 UTC

(In reply to clemens.brunner from comment #3)
> I don't think that this is a duplicate of 509253, and the proposed fix also
> doesn't work for me.
> 
> When trying to access a subdirectory of a valid Samba share via Dolphin
> (e.g., smb://server/share/subdir/deepdir), the following error appears:
> 
> Internal Error - Unknown error condition: [11] Resource temporarily
> unavailable

The symptom you describe don't correspond to the original report here either.
This error is nothing alike "No shared folders found" which was an application issue.
"Internal Error" is well a trickier issue.

> 
> The top-level share and its immediate subdirectory are accessible, but going
> one level deeper triggers the error. The same path works with GNOME Nautilus
> and smbclient (i.e., smbclient //server/share -U username; cd subdir/deepdir
> works). The server is part of an Active Directory domain and likely uses
> DFS. Dolphin seems to treat deep paths as new tree connects or mishandles
> DFC referrals.

That's a different issue altogether.
Feel free to open a new bug.
With as much information as possible, like the output of dolphin when launched from the commandline with the command:
QT_LOGGING_RULES="kf.kio.workers.smb.debug=true" dolphin
And reproducing the issue.

*** This bug has been marked as a duplicate of bug 509253 ***

Comment 5 clemens.brunner 2025-10-22 04:59:22 UTC

Thank you, I've created a new issue (Bug: 510902).