Prior to the latest version, there was a "Network" category/protocol in dolphin under "Network" that showed locally discovered avahi mdns/dnssd devices [like printers] that was very useful. It's gone now, and kde doesn't support network:/ at all. It says "invalid protocol" Currently on OpenSuSE TW, but verified that's gone and not working in Neon also. If that stuff is supposed to be under zeroconf now, I have never had zeroconf:/ [in 20+ yrs of KDE, across numerous distros] populate anything more than localhost. ---- Operating System: openSUSE Tumbleweed 20210820 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2
This was intentional; we weren't aware that this was useful for anything. When you do discover a printer with it, what can you do with it?
(In reply to Nate Graham from comment #1) > This was intentional; we weren't aware that this was useful for anything. > > When you do discover a printer with it, what can you do with it? If you're familiar with Windows network discovery, it works like that. It will show the device, and you could get information about it, or just double click the device and it would open the admin webpage. So, in my workplace, I admin a network with many printers and MFP's on the network. It was nice to be able to go to network:/, and see all network printers, expand their listing (which displayed the services they offered, including the admin web interface), launch that web interface link and have it open in the browser. network:/ used to give you mostly the same info/links that were presented by running "avahi-browse -rat".