| Summary: | When you call the network:/ then systems take about 5 minutes discover | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | boospy <linux> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | deano_ferrari, kdelibs-bugs-null, nate, sebastiankuzlak |
| Priority: | NOR | ||
| Version First Reported In: | 5.45.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
boospy
2016-11-03 16:47:52 UTC
Is this still an issue with KDE Frameworks 5.44 or greater? It still exists here on actual KDE-Neon. But what i find out: If you use the *.local with IPV4 this is working more better. But if you have an IPV6 network too and an real domain on avahi then you have to wait a very long time. Since an Upgrades after KDE 5.8 dolphin also can discover only a little piece of services. And they what are found are displayed wrong. Here is my config: [server] #host-name=foo domain-name=osit.cc #browse-domains=0pointer.de, zeroconf.org use-ipv4=no use-ipv6=yes #allow-interfaces=eth0 #deny-interfaces=eth1 #check-response-ttl=no #use-iff-running=no #enable-dbus=yes #disallow-other-stacks=no #allow-point-to-point=no #cache-entries-max=4096 #clients-max=4096 #objects-per-client-max=1024 #entries-per-entry-group-max=32 ratelimit-interval-usec=1000000 ratelimit-burst=1000 [wide-area] enable-wide-area=yes [publish] #disable-publishing=no #disable-user-service-publishing=no #add-service-cookie=no #publish-addresses=yes publish-hinfo=yes publish-workstation=yes #publish-domain=yes #publish-dns-servers=192.168.50.1, 192.168.50.2 #publish-resolv-conf-dns-servers=yes #publish-aaaa-on-ipv4=yes #publish-a-on-ipv6=no [reflector] #enable-reflector=no #reflect-ipv=no [rlimits] #rlimit-as= #rlimit-core=0 #rlimit-data=8388608 #rlimit-fsize=0 #rlimit-nofile=768 #rlimit-stack=8388608 #rlimit-nproc=3 Thanks for the information! I can also confirm that when using 'network:/' and 'zeroconf:/' to discover Avahi services, Dolphin is not working as expected. Refreshing (with F5) sometimes helps with zeroconf:/, but it is not consistent. Interestingly, using Gnome's Nautilus file manager does find the 'missing' remote shares consistently. I would like to know what the Dolphin KIOs are doing 'under the hood' that leads to the failure unreliability. I can get a 'complete' discovery output from 'avahi-browse -art' however, so I know all published services are present. If any additional information would help with the process of diagnosing and resolving this issue, I'm keen to assist to help progress it. Dolphin version 17.12.3 KDE Plasma 5.12.5 KDE Framework 5.45.0 (In reply to Dean from comment #5) > I can also confirm that when using 'network:/' and 'zeroconf:/' to discover > Avahi services, Dolphin is not working as expected. Refreshing (with F5) > sometimes helps with zeroconf:/, but it is not consistent. Interestingly, > using Gnome's Nautilus file manager does find the 'missing' remote shares > consistently. I would like to know what the Dolphin KIOs are doing 'under > the hood' that leads to the failure unreliability. I note that when I bounce a remote host's (DHCP) network connectivity, then Dolphin (network:/ KIO) suddenly (more often than not) displays that host as being available, but that seems to be all the only event than can trigger it. Dynamic detection does not seem to be occurring as one would hope. Still present in 2021... Frameworks 5.83.0 KDE 5.22 |