banshee fails to connect to functional mt-daapd server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Banshee |
Fix Released
|
Medium
|
|||
banshee (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: banshee
I just set up a DAAP server on my desktop computer using mt-daapd so I can connect from my laptop and listen to my music. However, I'm having a difficult time connecting to DAAP using Banshee. I can connect to the DAAP server from Banshee once in a while (and I'm not quite sure what the conditions are), but if I close Banshee entirely and re-open it later, I cannot connect to the server. Moreover, even when Banshee fails to connect, I can open Rhythmbox, and it connects correctly.
Steps to Reproduce:
1) Start mt-daapd on desktop using `sudo mt-daapd` command
2) Start Banshee on laptop. At this point, the DAAP share may or may not show up in the left column
3) Exit Banshee completely by right-clicking the icon in the notification area, and clicking "Exit"
4) Start Banshee on laptop again. This time, DAAP server almost always won't show up.
5) Start Rhythmbox on laptop. Notice that the DAAP server *does* show up in Rhythmbox
I'd like to emphasize that I still haven't found exactly what condition causes Banshee not to load the DAAP server. Most often it's after the second or third time running Banshee. However, sometimes it's not recognized on the first run, and sometimes it is recognized on subsequent runs.
I've attached the following log output:
mt-daapd-
banshee-
mt-daap-
I wasn't able to get a mt-daapd or banshee log of when banshee successfully connects, because I wasn't able to connect in ~10 attempts. I'll try again later, and post logs if it works out.
The versions of banshee and mt-daapd are the latest for Ubuntu Intrepid 8.10. Specifically:
banshee:
Installed: 1.4.1-1~intrepid1
mt-daapd:
Installed: 0.9~r1696.dfsg-2
The desktop and laptop are both running fairly standard installs of Ubuntu Intrepid. The desktop is running 64-bit version, and the laptop 32-bit. Please let me know if there is any further information I can provide.
Changed in banshee (Ubuntu): | |
status: | Incomplete → In Progress |
Changed in banshee: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
After playing around a little bit more, I've found a potential "workaround"-- or at least a way to force the shares to connect if they don't work at first:
1) Make sure mt-daapd server is running
2) Start Banshee. If the DAAP server doesn't show up:
3) In Banshee, go to Edit > Preferences
4) Select the "Extensions" tab, and find the "DAAP" plugin
5) Disable and re-enable the DAAP plugin. The shares should now show up in the left pane.
To me, this seems to imply that the Banshee DAAP plugin may be leaving some network resource open between sessions. However, it's hard to say, and I'm really in no position to start debugging into it. Hope this workaround is helpful in solving the problem. I've also attached two new logs:
mt-daapd- log-banshee- restart. txt: mt-daapd log file from /var/log/mt-daapd for a complete session, where banshee has been run and connects to DAAP using the steps listed above. restart- plugin. txt: console output of running `banshee --debug --debug-addins`, and connecting to the DAAP server using the workaround above.
banshee-