Description of problem: Avahi publishes details of ssh servers twice. Once using the service name 'Remote Access on hostname', and the other using the service name 'hostname' Version-Release number of selected component (if applicable): avahi-0.6.30-1.mga1 How reproducible: Every time. Using Dolphin or konqueror browse to zeroconf:/_sftp-ssh._tcp Two entries for each ssh server will appear The fix is quite simple. Remove the file /etc/avahi/services/sftp-ssh.service from the avahi package. The file /etc/avahi/services/openssh..service from the openssh-server package contains the same functionality as well as fish://
Hi, thanks for reporting this bug. Assigned to the package maintainer.
Keywords: (none) => TriagedAssignee: bugsquad => dmorganec
i am on it.
please test new avahi
Dave, I do not see avahi-0.6.30-5.mga2 in the Cauldron repo yet.
avahi-0.6.30-6.mga2 is now available. Please reopen if the bug is still valid.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Reopening Sorry it took so long to test. In avahi-0.6.30-5.mga2 the file /etc/avahi/services/sftp-ssh.service is gone, but now there is /etc/avahi/services/ssh.service with the same contents
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
CC: (none) => djmarian4uSummary: Avahi publishes ssh servers twice => avahi publishes ssh servers twice
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Still present on Mageia 2 As seen here, there are two entries for _ssh._tcp from the same server # avahi-browse --all -t + eth0 IPv4 Mythbackend on mythserver _mythbackend-master._tcp local + eth0 IPv4 Remote Access on mythserver _ssh._tcp local + eth0 IPv4 mythserver _ssh._tcp local + eth0 IPv4 Remote Access on mythserver _sftp-ssh._tcp local + eth0 IPv4 mythserver _udisks-ssh._tcp local + eth0 IPv4 mythserver [f4:6d:04:e4:ce:8a] _workstation._tcp local
Version: Cauldron => 2
Keywords: NEEDINFO => (none)
CC: (none) => marja11Version: 2 => CauldronWhiteboard: (none) => MGA2TOO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Assignee: dmorganec => bugsquad
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD