Red Hat Bugzilla – Bug 503424
k3b shows bad CDDB lookup information.
Last modified: 2014-01-12 19:09:09 EST
Trying to rip audio CD, k3b does a CDDB query, and returns with a dialog with the message "K3b found multiple inexact CDDB entries. Please select one."
In the selection box, the list of entries has one entry: "1 - (_)" (where the _ is a hollow square, probably an invalid character code).
Other apps (asunder) will correctly retrieve data for the same CDs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start K3b
2. Load audio CD into drive
3. Click on the drive
K3b says it is retrieving CDDB entry, then returns with above mention dialog, even if the disk has a unique entry according to other apps.
K3b will display CD information (if unique entry), or a valid list of alternatives.
Last I tried (admittedly awhile ago), it worked well. Is this reproducible with any audio cd, or just 1 (or 2) you tried?
This is reproducible with all audio CD's I tried (3 or 4). To verify reproducibility, I also tried this on a i586 install on a different system, and the behavior was the same.
On both these system, this was a mostly KDE install, i.e. on the installation, I deselected Gnome desktop, and selected KDE. Both systems were running with current "yum updates".
Thank you for taking the time to report this issue.
This is an issue that needs to be addressed by the upstream developers. Please report this at http://bugs.kde.org and then add the upstream report information to this report. We will monitor the upstream report for a resolution to this issue.
Fedora Bugzappers volunteer triage team
I found that it already exists as http://bugs.kde.org/show_bug.cgi?id=194868. It was originally reported there for F10, reconfirmed for F11 and Kubuntu 9.04.
Updates to the bug at KDE reveal this was apparently a bug (link in comment #4 above) with the CDDB provider defaulted to by k3b (freedb2.org). It appears that different tools use different providers, which is why it worked for asunder, but not k3b. freedb2 has apparently corrected their site, and k3b now works.
Sorry for the false bug.
Thanks Rick, stellar detective-work.