I'm not sure if this is the correct place to file this bug. I've filed directly with KDE, but it was suggested on the Gentoo IRC channel that I file this bug with Gentoo. I'm a bit frustrated here - the first time since installing Gentoo a year and a half ago. The problem started since I did an upgrade of kde3.4.3 to kde3.5.2. I used split ebuilds in both instances. In kde3.4.3, kaudiocreator worked flawlessly. Despite trying multiple times and despite removing the kaudiocreatorrc file in my /home/colleen/.kde3.5/share/config directory, the problem repeats itself constantly. The ripping process will start, but then it will freeze part way. The progress through the tracks on the CD that I am trying to rip varies, but inevitably it will freeze and I can't even kill the process with kill -9. Additionally, if I click the kaudiocreator application to close it and *if* I get a dialog box asking if I want to terminate the application, the application will terminate, but the process still shows if I run ps -ax. In this scenario, if I continue to use any application, ultimately everything with freeze and I will have to do a reset to reboot. If I leave kaudiocreator alone, all the other applications work fine.
I have some additional information in regard to this. The CD that I was trying to rip was a newly purchased one. I decide to try ripping a CD that I had previously had success ripping. I was able to rip the CD successfully. However not matter what I try, I cannot get the newly purchased CD to rip. The one that I was able to successfully rip, was actually released chronologically before the newly acquired one. However, the new on is not a new release. I have other CD's by this same artist that are newer than the one that I am trying to rip. So, it seems that kaudiocreator is somehow being fussy about what it will and won't rip. And as I said before, this situation is only since the transition from kde3.4.3 to 3.5.2.
>I'm not sure if this is the correct place to file this bug. I've filed directly with KDE, but it was suggested on the Gentoo IRC channel that I file this bug with Gentoo. When you're sure a problem is definitely KDE specific and not Gentoo related, it's fine, when you file your bug at https://bugs.kde.org. Otherwise here. But please do not file it in both bugzillas, watching which team is faster to track down your problem. That's wasting others time. Did you try to read the problematic cd both with KDE 3.4 and 3.5? Reading "newly purchased" as really new, I think of copy protected cd's, not complying to the Red Book standard, causing problems. Reading "the new one is not a new release", I assume you bought a used one and it may have scratches, causing reading problems and the code doesn't deal with it gracefully, but locks your box. When you start kaudiocreator in a shell, do you see any error output?
In reply to comment #3) (In reply to comment #2) > > When you're sure a problem is definitely KDE specific and not Gentoo related, > it's fine, when you file your bug at https://bugs.kde.org. Otherwise here. But > please do not file it in both bugzillas, watching which team is faster to track > down your problem. That's wasting others time. Well, unfortunately, in this instance I *did* file it in both places, but that was because I assumed that kaudiocreator was a kde app. I wasn't thinking about the fact that Gentoo had it's own kde team. I apologize and won't do it again! :-) However, to redeem myself, the suggestion to file in Gentoo was made my someone in the Gentoo forum where I had gone to see if I could get any insight into the problem. This person new that I had filed with kde upstream. > > > Did you try to read the problematic cd both with KDE 3.4 and 3.5? No, By the time I got this CD, I had already removed kde 3.4 from my system. All my sound applications worked fine - Noatun, xmms, amaroK, so I didn't anticipate a problem seeing as I was able to rip CD's no problem with kde 3.4. Reading "newly purchased" as really new, I think of copy protected cd's, not complying > to the Red Book standard, causing problems. Reading "the new one is not a new > release", I assume you bought a used one and it may have scratches, causing reading problems and the code doesn't deal with it gracefully, but locks your box. The CD is "new" meaning purchased new and shrinkwrapped. It was not a new release - the release date was 1991. As far as copy protection goes, I don't think this is the issue since I have ripped multiple CD from this same artist, the newest being a CD that was released in April 2006 and this ripped fine under kde 3.4. I just tried ripping the April 2006 release using kaudiocreator in kde 3.5 and it froze. kaudiocreator will read the tracks, but during the ripping process, it will freeze. These CD's also play fine in kscd. > > When you start kaudiocreator in a shell, do you see any error output? No. Regards, Colleen Beamer
I owe you a profound apology for filing this bug, since it wasn't a bug at all, but a failing CD-RW drive. The drive was working flawlessly prior to an upgrade to KDE 3.5, but afterwards, kaudiocreator was exhibiting strange behaviour. Since I had no indication prior to the upgrade that the drive was not working properly, I assumed it had to be something due to the upgrade. I have since purchased a new CD-RW drive, upgraded to KDE 3.5 and kaudiocreator and all applications that use the drive are working flawlessly. Again, my sincere apologies.
