Bug 282168

Summary: Enable freedb lookup/Query CDDB mismatch
Product: [Applications] k3b Reporter: Tristan Miller <psychonaut>
Component: generalAssignee: k3b developers <k3b>
Status: REPORTED ---    
Severity: normal CC: trueg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tristan Miller 2011-09-16 20:42:04 UTC 
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

In Settings->Configure k3b…->CDDB->Lookup, there is a checkbox labelled "Enable freedb lookup".  If this box is unchecked, the "Query CDDB"* icon rather confusingly still appears in the "Rip Audio CD" toolbar, though clicking on it has no effect.

If the settings option is meant to preclude the use of FreeDB altogether, then unchecking it should remove (or at least grey out) the corresponding icon from the toolbar.

However, there is an alternative solution which would preserve FreeDB functionality:  call the settings option instead "Enable automatic FreeDB lookup".  When it's disabled, k3b should not automatically consult FreeDB to find CD data for inserted discs.  However, the "Query CDDB" toolbar icon should remain active in case the user wishes to manually retrieve the FreeDB CD information.

*Technically, this icon should actually be labelled "Query FreeDB"; see Bug 269485.

Reproducible: Always

Steps to Reproduce:
1. In Settings->Configure k3b…->CDDB->Lookup, uncheck "Enable freedb lookup".

Actual Results:  
2. The "Query CDDB" icon still appears in the toolbar, though clicking on it has no effect.

Expected Results:  
3. The "Query CDDB" icon should be functional, but the configuration option should be renamed "Enable automatic freedb lookup".
Comment 1 Andrew Crouthamel 2018-11-12 02:43:17 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Tristan Miller 2018-11-13 19:42:08 UTC 
Confirming bug still exists, as originally described, in K3b 18.08.2.
Comment 3 Justin Zobel 2022-12-03 09:01:38 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Tristan Miller 2022-12-14 11:03:39 UTC 
Confirming that the problem still exists with K3b 22.08.3.