Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6417 - rhythmbox 0.9.7-3 daap support not working

Attached to Project: Arch Linux
Opened by Tor Krill (tor) - Wednesday, 14 February 2007, 13:24 GMT
Last edited by Jan de Groot (JGC) - Friday, 27 April 2007, 06:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Not 100% sure but i'm not able to play music shared over daap in rhythmbox any more. Neither with a collection shared from another rhythmbox nor from a device running mt-daapd.

This worked perfectly until upgrading one of the latest versions. Now using 0.9.7-3. On my other Archcomputer running 0.9.7-1 it works nicely.

What happens now is that when doulble clicking on one song from a daap-share, it lists nicely, rhythmbox immediately flags it with a little warning symbol and then proceeding rapidly through the complete share marking them in the same way. When later clicking on a file i get a dialog saying "Could not open resource for reading". When looking at the logs at mt-daap. Rhythmbox indeed makes the connection and starts requesting the song but then seems not to read any data.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 27 April 2007, 06:03 GMT
Reason for closing:  Fixed
Comment by Dennis (vitalstatistix) - Wednesday, 14 March 2007, 01:38 GMT
I am also experiencing this problem with rhythmbox - banshee plays well. could be a rb bug
Comment by Jan de Groot (JGC) - Thursday, 26 April 2007, 20:41 GMT
Is this fixed with the current version of rhythmbox?
Comment by Dennis (vitalstatistix) - Thursday, 26 April 2007, 22:43 GMT
Yes - I think the latest rb (0.10.0) fixes this issue.

Loading...