Jumping in as this problem affects my programming efforts also. I belive the core of the problem is, that the session-id is not a mandatory part with mt-daapd, but rhythmbox fails to use an URI that does not contain it.
This works with a browser (no session-id specified): http://192.168.0.105:3689/databases/1/items/690428.mp3 But with rb(0.11.6), it does not. (rhythmbox-client:12672): Rhythmbox-WARNING **: Method invoked for loadURI returned FALSE but did not set error If the action is coming outside of rb, or if rb is not even running yet, we don't have a valid session-id to use, and an invalid one doesn't work either, same error. I see a few possible solutions. Since ignoring the session-id is not a universal property of daap, and I have no idea how it handles with authentication turned on (never worked that great for me), it would be better if one could query for the session-id rb has, while rb gets a new one if it doesn't have one yet. This way an external program could construct a valid daap uri. On the other hand, since iTunes has gone crypted and so on, mt-daapd is probably what were stuck with for eternity. So, perhaps the faster fix of appending a session-id to queries without it could work as well. But it does add "extra" functionality to the org.gnome.Rhythmbox.Shell.loadURI method that realy shouldn't be there, so the first solution would be a lot better imo. -- Unable to start Rhythmbox DAAP playback from the command line or service-discovery-applet https://bugs.launchpad.net/bugs/178681 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
