After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 334823 - sound-juicer doesn't fetch CD info from the Internet
sound-juicer doesn't fetch CD info from the Internet
Status: RESOLVED FIXED
Product: sound-juicer
Classification: Applications
Component: metadata
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
: 335071 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-16 22:46 UTC by Sebastien Bacher
Modified: 2014-03-24 16:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-03-16 22:46:39 UTC
That bug has been described on https://launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/30308

"[Dapper]

When inserting an audio CD, sound-juicer launches but no information about the CD is downloaded.

On the other hand, if I launch rhythmbox, the CD appears in the left column and the track info is fetched automatically.
...
> Thanks for your bug. Do you have any error on the command line? Does it happen with all your CDs or only one?
...
When I filed the bug, I had tried with 4 or 5, none of them was recognized. I just tried with a few other CDs, and some of them are correctly recognized (this seems related to the CD's popularity ^^). Sound-juicer seems to always try to get info, but sometimes it comes back with nothing.

The weird thing is that rhythmbox always recognizes CDs very well, even the ones sound-juicer doesn't. Shouldn't they be searching from the same database ?

sound-juicer doesn't print anything when launched from the command line : it's perfectly quiet. Should I give some examples of unrecognized CDs ? Should I change the bug title into "sound-juicer should search the same CD database as rhythmbox" ?
...


Have the same behaviour here with ppc and i386. Does not happen in Breezy.
I export MUSICBRAINZ_DEBUG=true and then get the following with sound-juicer 2.13.{4,6}

  url: http://mm.musicbrainz.org:80/cgi-bin/mq_2_1.pl
query: <?xml version="1.0"?>
<rdf:RDF xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc = "http://purl.org/dc/elements/1.1/"
         xmlns:mq = "http://musicbrainz.org/mm/mq-1.1#"
         xmlns:mm = "http://musicbrainz.org/mm/mm-2.1#">
<mq:GetCDInfo>
   <mq:depth>2</mq:depth>
   <mm:cdindexid>8FsDc5De9N.Fu_VnUcb9l07xc1A-</mm:cdindexid>
</mq:GetCDInfo>
</rdf:RDF>

After the request is made, it is never renewed, even with file->reread cd.
I don't found where the data are cached.
Sound-juicer 2.12.2 (on breezy) make the request with the full toc :

  url: http://mm.musicbrainz.org:80/cgi-bin/mq_2_1.pl
query: <?xml version="1.0"?>
<rdf:RDF xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc = "http://purl.org/dc/elements/1.1/"
         xmlns:mq = "http://musicbrainz.org/mm/mq-1.1#"
         xmlns:mm = "http://musicbrainz.org/mm/mm-2.1#">
 <mq:GetCDInfo>
  <mq:depth>@DEPTH@</mq:depth>
    <mm:cdindexid>yLpf9vkwv33b55S8W0TVSwTOgfk-</mm:cdindexid>
    <mm:firstTrack>1</mm:firstTrack>
    <mm:lastTrack>18</mm:lastTrack>
    <mm:toc>
      <rdf:Seq>
       <rdf:li>
         <mm:TocInfo>
           <mm:sectorOffset>344792</mm:sectorOffset>
           <mm:numSectors>0</mm:numSectors>
         </mm:TocInfo>
       </rdf:li>
[...]
    </rdf:Seq>
    </mm:toc>
  </mq:GetCDInfo>



Same issue here.

In fact, MusicBrainz doesn't seem to at all be working well... is it really a good idea to use them? What's wrong with the old freedb stuff?"
Comment 1 Ross Burton 2006-03-17 08:34:16 UTC
FreeDB is so broken it's amazing.  You really don't want to go there.

What version of Sound Juicer is this?  2.13.6 removed the caching so that isn't an issue anymore.

I just verified that the Dapper SJ (2.14.0 currently) works fine for me.  I have a feeling what could be causing the problem but its more likely that you need to update.
Comment 2 Ross Burton 2006-03-19 13:25:32 UTC
*** Bug 335071 has been marked as a duplicate of this bug. ***
Comment 3 Ross Burton 2006-03-19 13:26:09 UTC
Discussion on #335071 revealed the cause of this and I've committed a fix that will be in 2.14.1.