#770: RAOP detects AirportExpress only after resetting network --------------------------+------------------------------------------------- Reporter: takkat | Owner: coling Type: enhancement | Status: new Milestone: | Component: module-raop-* Resolution: | Keywords: module-raop-discover network reset --------------------------+-------------------------------------------------
Comment(by takkat): Now things get somewhat complicated: * avahi-browse -t _raop._tcp doesn't say anything until a network reset. * avahi-browse then immediately finds attached ''airport.local'', as does PA * after a power off to the airport, PA only removes it from the list when I repeatedly try to select it. * '''but still, avahi-browse detects the (non-existent) ''airport.local'' device''' * only after performiing a network reset avahi-browse will not falsely detect the (removed) device * however, when switching the airport on again it will be detected smoothly as expected (i.e. no additional network reset is needed) I hope this information helps to further narrow the bug. What else do you need? -- Ticket URL: <http://pulseaudio.org/ticket/770#comment:10> PulseAudio <http://pulseaudio.org/> The PulseAudio Sound Server _______________________________________________ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets