Few Zeroconf Service Types Work in Dolphin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Network |
Fix Released
|
Medium
|
|||
dolphin (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
kdenetwork (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
When I add a service file to my /etc/avahi/
I automatically thought that I had done something wrong even though the service files worked in the last release fine so I tested them against the avahi-browse application and they worked fine there so this must be a fault in Dolphin and not the Avahi Zeroconf implementation. This gets a little bit more distorted when I add the ssh service file (a duplicate of the example file from the docs folder) and it displays as a fish service and connects as a fish service but shows up fine in the avahi-browse app mentioned earlier.
Example ssh.service file (That shows as a fish service in Dolphin):
<service-group>
<name replace-
<service>
<type>
<port>
</service>
Example smb.service file (That does bugger all in Dolphin):
<service-group>
<name replace-
<service>
<type>
<port>
</service>
Please can this be investigated please as it appears to have been borked between 8.04 and 8.10
1) The release of Ubuntu you are using: 8.10
2) The version of the package you are using: 4:4.1.3-
3) What you expected to happen: All possible service types to work.
4) What happened instead: Bugger All.
Changed in kde4libs: | |
status: | Incomplete → New |
Changed in kdenetwork (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in kdenetwork: | |
status: | Unknown → New |
Changed in kdenetwork: | |
importance: | Unknown → Medium |
Changed in kdenetwork: | |
status: | New → Fix Released |
This bug affects me too. I have three services declared in /etc/avahi/ services/ in three computers on my local network and I get only the ssh services through the konqueror/dolphin zeroconf:/ kioslave.
Here is the output of mdns-scan:
sim@bala:~$ mdns-scan _tcp.local _tcp.local _tcp.local 02:9b:26: e4]._workstatio n._tcp. local ssh._tcp. local smb._tcp. local fish._tcp. local 8d:50:0a: 37]._workstatio n._tcp. local _ssh._tcp. local _smb._tcp. local _fish._ tcp.local af:a7:52: 62]._workstatio n._tcp. local
+ Remote Terminal on bala._ssh.
+ Samba shares on bala._smb.
+ fish:/ prisijungimas į bala._fish.
+ bala [00:13:
+ Remote Terminal on pieva._
+ Samba shares on pieva._
+ fish:/ prisijungimas į pieva._
+ pieva [00:50:
+ Remote Terminal on meldas.
+ Samba shares on meldas.
+ fish:/ prisijungimas į meldas.
+ meldas [00:15:
Browsing ... \
When I enter plain zeroconf:/ into the browser, I get a folder
"Nutolęs diskas (fish)" (which means "Remote disk (fish)"
when I open it, I see a list of three entries "remote terminal on Hostname" - weird, I expected remote disks here !
and the browser address bar changes to:
zeroconf:/_ssh._tcp
But when I click on one of tose icons, I can get connected to a remote server through the fish protocol. So the zeroconf does not display most of the service types, and in part reports wrongly those it does detect.
I am using kde 4.1.3 on Kubuntu Intrepid.
There is a thread about this problem on forums.kde.org: forum.kde. org/kde4- networking- zeroconf- t-17141. html
http://