Bug 447118

Summary: Rhythmbox no longer automatically lists DAAP shares
Product: [Fedora] Fedora Reporter: W. Michael Petullo <mike>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-19 20:03:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description W. Michael Petullo 2008-05-17 23:56:33 UTC
Description of problem:
I use rhythmbox as my audio player and mt-daapd as my media server. Rhythmbox used to list my mt-
daapd DAAP share automatically because mt-daapd publishes its share using Avahi. Rhythmbox now 
does not list the share until I manually select Music -> Connect to DAAP Share. 

Version-Release number of selected component (if applicable):
rhythmbox-0.11.5-9.fc9.ppc

How reproducible:
Every time

Steps to Reproduce:
1. Install and configure mt-daapd
2. Start rhythmbox
  
Actual results:
Rhythmbox does not list mt-daapd's DAAP share.

Expected results:
Rhythmbox should list mt-daapd's DAAP share without the user manually connecting to it. This is how 
things worked out of the box when using F-8.

Additional info:
iTunes detects my mt-daapd DAAP share automatically as I would expect.

I tried to downgrade to a previous version of rhythmbox from F-8, but that did not fix the problem.

Comment 1 Bastien Nocera 2008-05-19 10:23:33 UTC
Could you please try disabling the firewalls on both machines, and restarting
Avahi (and Rhythmbox/mt-daapd as well).

Comment 2 W. Michael Petullo 2008-05-19 20:03:58 UTC
Yes, you got it.

Sorry, I had turned off the firewall on the mt-daapd server, but not my Rhythmbox client. I guess I didn't 
put much thought into how mDNS/DNS-SD works.

For the record, adding the following line to my client's /etc/sysconfig/iptables allows avahi through the 
client's firewall:

-A INPUT -m state --state NEW -m udp -p udp --dport 5353 -j ACCEPT

Comment 3 Bastien Nocera 2008-05-19 20:28:33 UTC
See bug 444427