SUMMARY Dolphin 21.04 doesn't show my workgroup anymore, despite of "client min protocol = NT1" in smb.conf. It used to work before and still does with GTK file browsers that utilize GvFS. Dolphin also doesn't show it when AVAHI is used for hostname resolution. STEPS TO REPRODUCE 1. Have an SMB1 server in your workgroup. 2. Try to discover it with Dolphin 21.04. OBSERVED RESULT It doesn't show up anymore. EXPECTED RESULT Not long ago, the workgroup still showed up in Dolphin under the "smb:/" path, it should do that again (21.04 regression?). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 5.11 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81 Qt Version: 5.15.2.
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves/Debugging_kio_smb#Reporting_Bugs
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Since it's not my network infrastructure, I won't be providing debug logs due to privacy reasons. Though it seems that currently something's fundamentally wrong with accessing SMB shares on Arch via userspace filesystem implementations , as I can't successfully open any share in Dolphin or Thunar (they repeatedly ask for credentials without success), whereas it works fine one Windows (and of course used to work before on Arch with no config changed in the meantime). So chances are it's not KDE related at all. If nobody intends to jump on this ticket train, I'd just close it.
Yeah if it also doesn't work for you in other apps (which have completely different underlying samba implementations) then there is definitely a problem either with the network's configuration, or your system's configuration.
Found out that the workgroup once again appears by adding "client max protocol = NT1" to smb.conf (which of course is bad). Seems Samba devs turned legacy compatibility into a nightmare, and I also still can't authenticate for accessing that SMB1 share.