Description of problem: I can no longer play tracks (either ogg or mp3) from my home daap server after upgrading the client to the latest version (0.11.3-1.fc8.i386). It worked with the previous version available in f8 (0.11.2-10.fc8.i386) Version-Release number of selected component (if applicable): 0.11.3-1.fc8.i386 How reproducible: 100%. Steps to Reproduce: 1. Open rhythmbox and click on daap server (in this case a server running rhythmbox 0.11.2-0ubuntu; hasn't been upgraded in weeks.) 2. Pick a song, any song. 3. double click on the song; nothing happens. (Should play.) 4. Try instead clicking on play; "Couldn't start playback Unknown playback error" pops up. Actual results: No music. Expected results: Music!
Does it happen for all file types, or just one type? Does enabling (or disabling) the cross-fading make it work?
Seems to happen on all the file types I have available (ogg and mp3), and they both play fine locally and over streaming radio. If I turn on cross-fading, the error changes from "Couldn't start playback Unknown playback error" to "Couldn't start playback (null)" but otherwise still fails.
Are you using mt-daap2 as well? (like Owen) I couldn't reproduce those problems locally, and playing music between an RB 0.11.2 and RB 0.11.3 machines work just fine. And I can't see very many changes between 0.11.2 and 0.11.3 that would result in DAAP stopping working. But it might be related to: http://bugzilla.gnome.org/show_bug.cgi?id=470711 or http://bugzilla.gnome.org/show_bug.cgi?id=390643 Any help from the mt-daap side? (debugging or whatever) Note that you can also use GStreamer to get debug information (see http://www.gnome.org/projects/totem/#bugs), or drag'n'drop the source file to totem or another application that understands HTTP for playback.
Nope, no mt-daap running. (Played with it a couple times but could never get it to work with ogg.) If I drag and drop from RB to totem, it says 'An error occurred location not found'. Not sure if that is useful or not. Oh, and on the command line, when following the steps described above, I get: (rhythmbox:9361): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry != NULL' failed
Beh. I can reproduce as well, I was using UPNP without realising :)
Rhythmbox-Message: rb_shell_player_entry_activated_cb: Entry has playback URI Unknown (location: daap://192.168.1.106:3689/databases/1/items/4.mp3?session-id=136937119, mount: Unknown) Probably a fallback from the work to support stream URLs.
Work-around at: http://koji.fedoraproject.org/koji/taskinfo?taskID=244951 Does it work for you, Luis? Unconvincing analysis at: http://bugzilla.gnome.org/show_bug.cgi?id=497430
Works like a charm...
rhythmbox-0.11.3-3.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rhythmbox'
rhythmbox-0.11.3-3.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.