Bug 382351

Summary: DAAP appears to no longer work with latest upgrade
Product: [Fedora] Fedora Reporter: Luis Villa <luis>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: 0.11.3-3.fc8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-20 17:46:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Luis Villa 2007-11-14 12:58:03 UTC
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):

How reproducible:

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:

Comment 1 Bastien Nocera 2007-11-14 13:09:17 UTC
Does it happen for all file types, or just one type?
Does enabling (or disabling) the cross-fading make it work?

Comment 2 Luis Villa 2007-11-14 13:32:58 UTC
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

Comment 3 Bastien Nocera 2007-11-16 13:27:44 UTC
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:

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.

Comment 4 Luis Villa 2007-11-16 13:50:05 UTC
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

Comment 5 Bastien Nocera 2007-11-16 15:01:36 UTC
Beh. I can reproduce as well, I was using UPNP without realising :)

Comment 6 Bastien Nocera 2007-11-16 16:58:15 UTC
Rhythmbox-Message: rb_shell_player_entry_activated_cb: Entry has playback URI
Unknown (location:
daap://, mount:

Probably a fallback from the work to support stream URLs.

Comment 7 Bastien Nocera 2007-11-16 17:21:42 UTC
Work-around at:

Does it work for you, Luis?

Unconvincing analysis at:

Comment 8 Luis Villa 2007-11-16 19:16:54 UTC
Works like a charm...

Comment 9 Fedora Update System 2007-11-17 05:38:06 UTC
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'

Comment 10 Fedora Update System 2007-11-20 17:46:01 UTC
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.