This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Unreliable network:/ and zeroconf:/ KIO behaviour

Tags: None
(comma "," separated)
Dean
Registered Member
Posts
6
Karma
0
I've been playing with the 'network:/' and 'zeroconf:/' KIOs to discover Avahi services via Dolphin, and found that it does not work consistently as expected. Refreshing (with F5) sometimes helps with zeroconf:/, but not consistently. By contrast, I have found that 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 that I'm observing. I can get a 'complete' discovery output from 'avahi-browse -art' however, so I know all published services are present. Anyone else got any ideas or experience with this? It would be great to have it working properly.

Dolphin version 17.12.3
KDE Plasma 5.12.5
KDE Framework 5.45.0
nmset
Registered Member
Posts
67
Karma
0
OS
This will certainly not help you, I'm just finding an exact misbehaviour of dolphin while nautilus browses avahi FTP shares seemlessly.

KDE Frameworks 5.49.0
Qt 5.11.1
User avatar
zachus
Registered Member
Posts
56
Karma
0
OS
and won't help me either.

a working line to enter in nautilus , by contrast, would be more helpful.

such as

zeroconf:/127.0.0.1

did not get me anywhere with nautilus nor dolphin

of course, we need confirmed working stuff. ;)


nmset
Registered Member
Posts
67
Karma
0
OS
Just checked with Dolphin 18.12.0, KDE Frameworks 5.53.0, Qt 5.12.0 :

It's just working magically !
Dean
Registered Member
Posts
6
Karma
0
Thanks for the update. That's good to know. FWIW, I'd like to see the Dolphin 'network:/' KIO utilize Avahi discovery a little more comprehensively. It could report a GUI version of 'avahi-browse -art' to report Avahi-published services offered by hosts on the LAN.


Bookmarks



Who is online

Registered users: Bing [Bot], gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]