Version: (using KDE 4.2.3) OS: Linux Installed from: Ubuntu Packages Hi I tried using zeroconf:/ to browse & discover devices and services that are advertising on the local domain. I get no errors but then also no results in Dolphin or Konquerer. Unfortunately I can't find a way to debug this easily. I've reported this on Launchpad for Kubuntu but thought there may be more interest here. Any ideas on what may be the cause? Here's a copy of the bug report: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/380288 ====== I've been tinkering with this for a while and have hit a brick wall. Not matter what I do, the zeroconf:/ stubbonly refuses to work in both konq and dolphin. System : Kubuntu 9.04 with 4.2.3 packages installed and up to date. System has avahi installed and running. avahi-discover, avahi-browse and mdns-scan all report services broadcasting. Typing zeroconf:/ into the url bar does not bring up any errors and is available in remote:/ as "network services" Packages installed: $ aptitude search avahi | grep "^i" i avahi-autoipd - Avahi IPv4LL network address configuration i avahi-daemon - Avahi mDNS/DNS-SD daemon i avahi-discover - Service discover user interface for avahi i avahi-dnsconfd - Avahi DNS configuration tool i avahi-utils - Avahi browsing, publishing and discovery u i bzr-avahi - mDNS plugin for Bazaar i libavahi-client3 - Avahi client library i libavahi-common-data - Avahi common data files i libavahi-common3 - Avahi common library i libavahi-compat-libdnssd1 - Avahi Apple Bonjour compatibility library i libavahi-core5 - Avahi's embeddable mDNS/DNS-SD library i A libavahi-glib1 - Avahi glib integration library i libavahi-qt3-1 - Avahi Qt 3 integration library i libavahi-qt4-1 - Avahi Qt 4 integration library i python-avahi - Python utility package for Avahi $ sudo aptitude search mdns i libnss-mdns - NSS module for Multicast DNS name resolution i mdns-scan - Scan for mDNS/DNS-SD services published on the local network kde-zeroconf is installed as well. avahi-discover: Browsing domain 'local' on -1.-1 ... Browsing for services of type '_http._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_rsp._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_daap._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_afpovertcp._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_raop._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_sleep-proxy._udp' in domain 'local' on 2.0 ... Browsing for services of type '_workstation._tcp' in domain 'local' on 2.0 ... Browsing for services of type '_airport._tcp' in domain 'local' on 2.0 ... Found service 'tomato on tomato' of type '_http._tcp' in domain 'local' on 2.0. Found service 'tomato on tomato' of type '_rsp._tcp' in domain 'local' on 2.0. Found service 'tomato on tomato' of type '_daap._tcp' in domain 'local' on 2.0. Found service 'tomato (AFP)' of type '_afpovertcp._tcp' in domain 'local' on 2.0. Found service 'pinky' of type '_airport._tcp' in domain 'local' on 2.0. mdns-scan $ mdns-scan + tomato (AFP)._afpovertcp._tcp.local + tomato on tomato._http._tcp.local + tomato on tomato._rsp._tcp.local + tomato on tomato._daap._tcp.local + pinky._airport._tcp.local (a few services removed there on purpose) So avahi seems to be working but the zeroconf:/ url in Konq and dolphin isn't picking this up (i assume it uses avahi behind the scenes). I tried configuring service discovery with .local domain in "network settings" of System Settings but nothing either, both apps just show an empty page where the services should be found. How could I debug what happens when zeroconf:/ is entered in the url bar of Konq and Dolphin? I'm wondering if zeroconf is broken in Kubuntu KDE -- Does it work for anyone else? Amarok is able to discover daap shares so I assume it's somehow working. What I'm expecting (and have seen before in KDE) is that a list of available services is shown in konq & dolphin Thanks in advance. =========
See also: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/311258
seems to be working in 4.9
Issue still reproducible for me in KDE 4.10.3. I need to fill another ticket or maybe it's possible to reopen this one?