K3b CDDB Error

Janusz11 · 10-07-2006, 02:29 PM

Hello all!

I just made a copy of two music CDs and K3b gave me the following error message:
"Cddb error (Error while connecting to host.)."

The burned CDs are ok, I can play them on my CD player. But I'd like to know what the error message could mean. System is a freshly installed Zenwalk 3.0.

Thanks in advance.

David the H. · 10-08-2006, 01:27 AM

CDDB is the CD Database. It's an online repository of the disk titles and track names. K3B can use this information to rip a disk to audio file with all the proper information included already, or to insert cd-text into a burned disk (cd-text is embedded track information that some cd players can read and display).

It's not a necessity, especially when you're just copying a disk, but it can be nice to have. Yours seems to be having connection problems, so if you're worried about it, first take a look in the k3b options and make sure it's set up right. You need to have an email address, for example (but it doesn't have to be a real one). The problem could have been on the network or CDDB end as well, though.

Janusz11 · 10-08-2006, 08:04 AM

Thanks mate.

I tried different settings now and found out that the best way is to disable CDDB in K3B altogether. I changed the internet addresses according to http://www.freedb.org/ and searched the net some more but couldn't find anything that could stop this error message.
Btw., where am I supposed to put in an e-mail address? Couldn't find anything for this in K3B.

Anyway, as long as the burning works I'm happy. Thanks again.

David the H. · 10-08-2006, 09:55 AM

Actually, I don't know. I went and looked through the config settings and I can't find it either. Nearly every other cddb-supporting program I've seen has asked for an address though. Now that I think of it, maybe it's only necessary for submitting new disks to the DB.

I don't know why yours isn't making a connection though. It should be automatic. But diagnosing connection problems is getting out of my league. It could just be a temporary problem. There have been several times for me when a K3B update has broken something, sometimes seriously, but the next update usually fixes it.