Version: (using KDE KDE 3.1.1) Installed from: RedHat RPMs OS: Linux KDE Packages Used: RedHat 8.0 Contribution for KDE 3.1.1 System: Redhat 8.0+errata fixes kscd is unable to do any CD lookups on my work computer. The following appears in the console kscd is started from: CDTEXT INFO: use GET_FEATURE_LIST(0x46)... CDTEXT INFO: try to read, how long CDTEXT is? CDTEXT INFO: CDTEXT is a 7 byte(s) long CDTEXT INFO: try to read CDTEXT CDTEXT ERROR: READ_TOC(0x43) with format code 0x05 not implemented or broken. ret = -1! CDTEXT INFO: free_cdtext_info() called GNOME's gnome-cd has no issues doing CDDB lookups on the same computer.
Subject: Re: New: KSCD cannot do CDDB Lookups On Monday 24 March 2003 01:15, you wrote: > kscd is unable to do any CD lookups on my work computer. silly question: are online CDDB lookups enabled in the KsCD configuration dialog? if so, are you behind a proxy/firewall or any other such situation? if you are able to, does a network monitor such as ethereal show any outgoing CDDB traffic from KsCD? > The following > appears in the console kscd is started from: CDTEXT INFO: use > GET_FEATURE_LIST(0x46)... > CDTEXT INFO: try to read, how long CDTEXT is? > CDTEXT INFO: CDTEXT is a 7 byte(s) long > CDTEXT INFO: try to read CDTEXT > CDTEXT ERROR: READ_TOC(0x43) with format code 0x05 not implemented or > broken. ret = -1! CDTEXT INFO: free_cdtext_info() called this is fine, and doesn't have anything to do with CDDB... thanks for the report.
Pardon me; this seems to be a complex mess of things. Partially my fault, partially possibly kscd's, and possibly partially the RedHat packages: Checked out at home using Gentoo packages and my configuration file from work (with the freedb directory changed): 1. One of the issues indeed was that "Enable remote freedb" was disabled. However, given the fact that kscd started up stating "No matching freedb entry found," the freedb server was set (as per default) to "freedb.freedb.org cddbp 8880 -" and kscd spat out the CDTEXT errors every time I started kscd or pressed the "Fetch Info" button in the freedb/CD Database Editor, I was lead to believe that freedb was running. (Enhancement proposal: clarify the freedb configuration system and the freedb dialog box. A Winamp-ish system is likely desired: no remote queries, always query remotely, or query remotely only when "Fetch info" is pressed (for dialup users). An informative box should appear if "Fetch Info" is pressed and remote lookups are fully disabled.) 2. Problem #1 also occured on my home computer when the file I used from work was used, or I deleted ~/.kde/share/config/kscdrc and let kscd recreate it. My computer, which used to not have the CDTEXT error problem, started having it as well. This leads me to believe that when kscd is forced to initialize its own configuration file, it either improperly sets or fails to set some parameters. (Bug report/minor/non-function imparing: kscd does not seem to initalize its configuration properly upon first startup). It is therefore also likely that the RH 8.0 packages require kscd to write its own configuration file, while I have one at home written by something else (possibly kcontrol or an older kscd revision?). ---- *Still*, I do not get all the problems at home that I get at work: I. Kscd (RH 8 package version) does not minimize to the system tray when the quit (X) button is pressed (Enhancement proposal: Don't use the quit button in the kscd window for minimization. Minor bug: don't make someone have to use the quit dialog in the system tray icon twice - first to close the kscd window, then to close the icon itself). However, kscd is still running in the background, and attempts to restart it will result in the comment "kscd is already running!" The stale kscd process then needs to be killed by hand in order to allow kscd to start up again. This error is specific to my work RH 8 system. 2. I also have bug #55976 at work, but not at home. kscdrc files being used: http://www.cerlyn.com/kscdrc-good.txt - this one has no problems. I'm not sure what generated it though (Gentoo machine). I believe the ~/.cddb directory was my own doing so kscd would share freedb data with other applications (I have since forgotten what). http://www.cerlyn.com/kscdrc-bad.txt - this is the one from the RedHat machine, and is identical to the auto-generated one from the good machine except for the freedb directory. It gets the CDTEXT errors, as does the kscd auto-generated one on the good machine, while using the kscdrc-good.txt configuration does not. Next, I will try my home configuration file at work to see if it fixes anything (work is firewalled off, which is why this is taking so long).
Subject: Re: KSCD cannot do CDDB Lookups On Thursday 27 March 2003 07:10, you wrote: > 1. One of the issues indeed was that "Enable remote freedb" was disabled. > However, given the fact that kscd started up stating "No matching freedb > entry found," the freedb server was set (as per default) to > "freedb.freedb.org cddbp 8880 -" and kscd spat out the CDTEXT errors every > time I started kscd or pressed the "Fetch Info" button in the freedb/CD yes, there should be better feedback as to what is going on.. i'll look into this for 3.2... > 2. Problem #1 also occured on my home computer when the file I used from > work was used, or I deleted ~/.kde/share/config/kscdrc and let kscd > recreate it. My computer, which used to not have the CDTEXT error > problem, started having it as well. the CDTEXT messages are not a problem. they are just informative and can safely be ignored. in fact, in 3.2 final release packages won't have that text at all. but again: they are not a sign of a bug or a problem. basically kscd has been told to look for CDTEXT blocks and they aren't there or aren't findable. no big deal. > I. Kscd (RH 8 package version) does not minimize to the system tray when > the quit (X) button is pressed (Enhancement proposal: Don't use the quit this has been fixed in CVS for some time.
Assuming that the kscd not appearing nor minimizing in/to the system tray has been fixed (on certain systems only?), all we have is a duplicate of bug #55976 then. The only curious thing about this duplication (besides all the other stuff showing up around it) is that I have seen that if you get prompted to choose one of several CDDB entries, pressing "Cancel" in that dialog actually will avoid causing a crash. Sorry about the big runaround; I could have sworn I searched for every outstanding current kscd issue in bugzilla prior to filing this. Obligatory but likely uneeded screenshot of the "not in system tray problem": http://www.cerlyn.com/kscd.jpg (1280x1024, rather compressed). Yes, I did hit "Apply" and "OK" after selecting "Show icon in system tray"; in fact, I went though the configuration menu several times. Klipper (in the system tray by itself) has no issues with its use.
*** This bug has been marked as a duplicate of 55976 ***