Hello, I am currently using the WSDD daemon to discover devices that share directories through WSD, however I have noticed that dolphin does not show the devices that are discovered. This happens with the original project recovered from https://github.com/christgau/wsdd but with the fork called wsdd2 it works perfectly. So I open this thread to review the problem. I start by sending the WSDD log showing that the Windows 10 device is discovered. ~ wsdd -D -v ✔ 54s 07:47:14 PM 2024-11-28 19:47:18,532:wsdd WARNING(pid 109983): no interface given, using all interfaces 2024-11-28 19:47:18,532:wsdd INFO(pid 109983): using pre-defined UUID c3e195f5-cece-40a4-9760-9ae807e243d9 2024-11-28 19:47:18,534:wsdd INFO(pid 109983): joined multicast group 239.255.255.250 on 192.168.3.2%wlan0 2024-11-28 19:47:18,535:wsdd INFO(pid 109983): scheduling Hello message via wlan0 to 239.255.255.250%wlan0 2024-11-28 19:47:19,544:wsdd INFO(pid 109983): scheduling Probe message via wlan0 to 239.255.255.250%wlan0 2024-11-28 19:47:19,545:wsdd INFO(pid 109983): joined multicast group 239.255.255.250 on 192.168.122.1%virbr0 2024-11-28 19:47:19,546:wsdd INFO(pid 109983): scheduling Hello message via virbr0 to 239.255.255.250%virbr0 2024-11-28 19:47:21,561:wsdd INFO(pid 109983): scheduling Probe message via virbr0 to 239.255.255.250%virbr0 2024-11-28 19:47:21,562:wsdd INFO(pid 109983): joined multicast group [ff02::c] on fe80::1c14:925a:ae49:dcf6%wlan0 2024-11-28 19:47:21,562:wsdd INFO(pid 109983): scheduling Hello message via wlan0 to ff02::c%wlan0 2024-11-28 19:47:22,565:wsdd INFO(pid 109983): scheduling Probe message via wlan0 to ff02::c%wlan0 2024-11-28 19:47:22,576:wsdd INFO(pid 109983): 192.168.122.37 - - "POST /c3e195f5-cece-40a4-9760-9ae807e243d9 HTTP/1.1" 200 - 2024-11-28 19:47:22,578:wsdd INFO(pid 109983): 192.168.122.37 - - "POST /c3e195f5-cece-40a4-9760-9ae807e243d9 HTTP/1.1" 200 - 2024-11-28 19:47:24,703:wsdd INFO(pid 109983): 192.168.122.37:3702(virbr0) - - "ProbeMatches urn:uuid:8d76a027-f9fc-45aa-9afb-23ab18379d15 UDP" - - /usr/bin/wsdd:649: DeprecationWarning: Testing an element's truth value will always return True in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. if (host_sec): 2024-11-28 19:47:24,732:wsdd INFO(pid 109983): discovered WIN10 in Workgroup:WORKGROUP on 192.168.122.37
Please fill in the reporting template. And please provide logs https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves/Debugging_kio_smb#Reporting_Bugs SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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
SUMMARY Dolphin does not show shared resources from another computers on multiple LAN and virtual LAN anouncing via WSDD. STEPS TO REPRODUCE Open dolphin Go to network Go to shared folders (SMB) Wait for a minut and see what hosts has been discovered OBSERVED RESULT Devices are only discovered on a single LAN, which is typically the one associated with the default gateway. EXPECTED RESULT All devices on all LANs to which the device is connected must be discovered. Since the WSDD daemon shows evidence of the discovery on all interfaces. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.13-1-lts (64-bit) Graphics Platform: X11 KDE FRAMEWORKS: 6.11 DOLPHIN VERSION: 24.12.2 LIBSMBCLIENT VERSION: 4.21.3 SAMBA VERSION: 4.21.3 HARDWARE Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 38.6 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming A15 FA506QM_FA506QM System Version: 1.0 ADDITIONAL INFORMATION This happens with all neighboring devices, it can be Windows in its different versions or different Linux distributions. The expected behavior is obtained in other desktop environments that use GVFS for this task. From what I see, I am being asked for SMB logs, however, there is no problem with SMB, SMB works correctly if I enter the specific path I want to enter, the problem is with the discovery via WSDD in which in dolphin it is displayed as wsdd.discovery or something similar.
Created attachment 178483 [details] smb log
[ 0.311](205158)/(default) unknown: QUdpSocket::setMulticastInterface() called on a QUdpSocket when not in QUdpSocket::BoundState this certainly sounds interesting. I think we'll need detailed steps on how to replicate your setup though.
(In reply to Harald Sitter from comment #4) > [ 0.311](205158)/(default) unknown: QUdpSocket::setMulticastInterface() > called on a QUdpSocket when not in QUdpSocket::BoundState > > this certainly sounds interesting. > > I think we'll need detailed steps on how to replicate your setup though. What kind of additional steps do you need?
As many as you can think of. Most notably how to replicate your multiple LAN setup.
(In reply to Harald Sitter from comment #6) > As many as you can think of. Most notably how to replicate your multiple > LAN setup. You can use virt-manager for create LANs using libvirt, ubridge, etc. I have two LANs created with this way. What Linux distro are you using?
(In reply to Mario from comment #7) > (In reply to Harald Sitter from comment #6) > > As many as you can think of. Most notably how to replicate your multiple > > LAN setup. > > You can use virt-manager for create LANs using libvirt, ubridge, etc. I have > two LANs created with this way. > > What Linux distro are you using? KDE Linux. Distro doesn't really matter though, we just need steps to replicate the setup if they target a specific distro that's fine too.
(In reply to Harald Sitter from comment #8) > (In reply to Mario from comment #7) > > (In reply to Harald Sitter from comment #6) > > > As many as you can think of. Most notably how to replicate your multiple > > > LAN setup. > > > > You can use virt-manager for create LANs using libvirt, ubridge, etc. I have > > two LANs created with this way. > > > > What Linux distro are you using? > > KDE Linux. Distro doesn't really matter though, we just need steps to > replicate the setup if they target a specific distro that's fine too. Well, I understand that's ubuntu based distro, so: sudo apt install virt-manager sudo systemct enable --now libvirtd sudo virt-manager Select qemu/kvm and click on edit Go to connection details Go to virtual networks Create one or more virtual networks Finally, create VMs using that virtual adapters.
What's the configuration for the virtual networks?
(In reply to Harald Sitter from comment #10) > What's the configuration for the virtual networks? There is a default virtual network called default and its device name is virbr0, you can create other as open network NAT or routed and get the same error. In my case I tested with routed, open and default virtual network.
A possibly relevant merge request was started @ https://invent.kde.org/network/kio-extras/-/merge_requests/409
Git commit 9e4d726b293bb0e5c87916a37a54d68b81e89a2f by Harald Sitter. Committed on 24/02/2025 at 13:27. Pushed by sitter into branch 'master'. smb: start WSDResolver's client before sending messages otherwise the messages may end up not getting sent because the socket is not bound. M +1 -0 smb/wsdiscoverer.cpp https://invent.kde.org/network/kio-extras/-/commit/9e4d726b293bb0e5c87916a37a54d68b81e89a2f
Git commit 74128f082dda8b001774a119685a8da189739dd0 by Harald Sitter. Committed on 24/02/2025 at 13:39. Pushed by sitter into branch 'release/24.12'. smb: start WSDResolver's client before sending messages otherwise the messages may end up not getting sent because the socket is not bound. (cherry picked from commit 9e4d726b293bb0e5c87916a37a54d68b81e89a2f) Co-authored-by: Harald Sitter <sitter@kde.org> M +1 -0 smb/wsdiscoverer.cpp https://invent.kde.org/network/kio-extras/-/commit/74128f082dda8b001774a119685a8da189739dd0
Hello Harald, today I updated to kio-extra 24.12.3 and get same error, I can't watch any device. export KDE_FORK_SLAVES=1 export QT_MESSAGE_PATTERN='[%{time process}](%{pid})/(%{category}) %{function}: %{message}' export QT_LOGGING_RULES='kf.kio.workers.smb=true;log_kio_smb=true' dolphin --new-window smb:// [ 0.000](4842)/(kf.kio.workers.smb) unknown: auth_initialize_smbc [ 0.000](4842)/(kf.kio.workers.smb) unknown: Setting debug level to: 0 [ 0.000](4842)/(kf.kio.workers.smb) unknown: Using libsmbclient library version QVersionNumber(4.21.4) [ 0.000](4842)/(kf.kio.workers.smb) unknown: QUrl("smb://") [ 0.000](4842)/(kf.kio.workers.smb) unknown: checkURL QUrl("smb://") [ 0.000](4842)/(kf.kio.workers.smb) unknown: updateCache "" [ 0.000](4842)/(kf.kio.workers.smb) unknown: Adding modern discovery (dnssd/wsdiscovery) [ 0.023](4842)/(kf.kio.workers.smb) unknown: Modern discovery set up. [ 0.023](4842)/(kf.kio.workers.smb) unknown: Starting discovery. [ 0.000](4845)/(kf.kio.workers.smb) unknown: auth_initialize_smbc [ 0.000](4845)/(kf.kio.workers.smb) unknown: Setting debug level to: 0 [ 0.000](4845)/(kf.kio.workers.smb) unknown: Using libsmbclient library version QVersionNumber(4.21.4) [ 0.000](4845)/(kf.kio.workers.smb) unknown: QUrl("smb://") smbXcli_negprot_smb1_done: No compatible protocol selected by server. smbXcli_negprot_smb1_done: No compatible protocol selected by server. [ 0.302](4842)/(kf.kio.workers.smb) unknown: open "smb://" url-type: 1 dirfd: 10000 errNum: 0 [ 0.302](4842)/(kf.kio.workers.smb) unknown: smbc_readdir [ 0.302](4842)/(kf.kio.workers.smb) unknown: done with smbc [ 9.871](4842)/(kf.kio.workers.smb) unknown: Discovery finished. [ 9.878](4842)/(kf.kio.workers.smb) unknown: QUrl("smb://") [ 9.878](4842)/(kf.kio.workers.smb) unknown: checkURL QUrl("smb://") [ 9.879](4842)/(kf.kio.workers.smb) unknown: updateCache ""
Hello, is there some news?