Bug 845846

I have been getting this quite frequently, but I am getting some that have the information populated in the fields to be ripped as well. Usually the code for my particular C.D. isn't associated with the album, but I don't know how to associate them. Have you tried "CD Lookup" with picard when sound-juicer fails to load the content? Usually - for me - the album's information is in the database, but the key for the particular release that I have isn't associated with the album. Once you've tried picard, is this the same for you?

Name        : sound-juicer
Arch        : x86_64
Version     : 3.5.0
Release     : 2.fc18

I wish that there was a way for this information to be used since it is somehow associated (e.g. picard knows what the album is and brings a list of releases).

Knowing that picard works in a specific case might help the maintainer identify the problem, but it doesn't help me as the bug reporter.  The maintainer would have to duplicate the problem on a physical CD that he owns, since he can't access mine.

Also, this bug is against F17, not F18.  Your problem may not be related at all.  Please file a separate bug if you're having a problem on F18.

I see the same behaviour - sound-juicer fails to find information for any CDs, even those I've previously successfully ripped using it. picard locates the same CDs without any trouble.

This is likely to be caused by http://tickets.musicbrainz.org/browse/LMB-34 , building packages with this patch applied now.

libmusicbrainz5-5.0.1-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/libmusicbrainz5-5.0.1-5.fc17

libmusicbrainz5-5.0.1-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libmusicbrainz5-5.0.1-5.fc19

Package libmusicbrainz5-5.0.1-5.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libmusicbrainz5-5.0.1-5.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4853/libmusicbrainz5-5.0.1-5.fc19
then log in and leave karma (feedback).

Installing libmusicbrainz5-5.0.1-5.fc17 didn't fix the issue for me on Fedora 17 64-bit. sound-juicer-3.4.0-1.fc17.x86_64 depends on libmusicbrainz4-4.0.3-3.fc17.x86_64

(In reply to comment #8)
> Installing libmusicbrainz5-5.0.1-5.fc17 didn't fix the issue for me on
> Fedora 17 64-bit. sound-juicer-3.4.0-1.fc17.x86_64 depends on
> libmusicbrainz4-4.0.3-3.fc17.x86_64

Ah that's an oversight on my side, thanks for catching that! Can you test this scratch build http://koji.fedoraproject.org/koji/taskinfo?taskID=5241494 ?

(In reply to comment #9)
> (In reply to comment #8)
> > Installing libmusicbrainz5-5.0.1-5.fc17 didn't fix the issue for me on
> > Fedora 17 64-bit. sound-juicer-3.4.0-1.fc17.x86_64 depends on
> > libmusicbrainz4-4.0.3-3.fc17.x86_64
> 
> Ah that's an oversight on my side, thanks for catching that! Can you test
> this scratch build
> http://koji.fedoraproject.org/koji/taskinfo?taskID=5241494 ?

Thanks for the quick response. This new build fixes the issue.

libmusicbrainz4-4.0.3-4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/libmusicbrainz4-4.0.3-4.fc17

libmusicbrainz5-5.0.1-5.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

libmusicbrainz5-5.0.1-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

libmusicbrainz4-4.0.3-4.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.