Description of problem: I tried to copy 1 track of a audio CD to another blank CD Version-Release number of selected component (if applicable): k3b 3.5.9.5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: got dialogs saying kio_audiocd and wodim were running already I answered yes kill those other processes failure produced the attached screen snapshot Expected results: track 20 copy Additional info:
Created attachment 304326 [details] snapshot of the screen after failure
According to the screenshot a possible buffer underun is to blame. Did you try as recommended and lower the burning speed?
Possibly related to bug #411701
No! I switched to Nero on XP Prof and burned the track! I'll try the lower speed (after I research to figure out how to do that)!
I couldn't find a set burn speed! Only a set read speed!
Its on the burn dialog window. Upper right corner next to the medium/drive selection. Its labeled Speed.
Created attachment 304350 [details] screen snapshot screensnapshot
I switched to a 1X speed and the program switched to 4X the copy is proceeding but the entire CD is being copied instead of trach 20! I only dragged down track 20. CDDB correctly identified the CD
and...the resulting CD does not load into any device but Fedora 8 playing the CD with Kaffeine works!
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Is this still an issue with F9? If so you should file a bug against k3b at bugs.kde.org and update this report with the upstream info. We will continue to monitor for a resolution.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.