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.
banshee-restart-plugin.txt: console output of running `banshee --debug
--debug-addins`, and connecting to the DAAP server using the workaround above.
** Attachment added: "mt-daapd log of banshee connecting to server using
workaround"
http://launchpadlibrarian.net/20448967/mt-daapd-log-banshee-restart.txt
--
banshee fails to connect to functional mt-daapd server
https://bugs.launchpad.net/bugs/308233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
