Bug 144954 - Won't rip then burn (same drive) from audio CD in one step
Summary: Won't rip then burn (same drive) from audio CD in one step
Status: RESOLVED UNMAINTAINED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-02 13:38 UTC by Francois Marier
Modified: 2010-03-16 16:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Marier 2007-05-02 13:38:29 UTC
Version:           1.0.1 (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Adam Porter <adam@alphapapa.net> has reported the following on the Debian bug tracker (http://bugs.debian.org/421865):

In k3b 0.12, you could put an audio CD in your CD-RW drive, make a new audio
CD project in k3b, drag the tracks from the top pane (representing the
inserted audio CD) to the bottom pane, click Burn, and k3b would rip the
tracks, eject the audio CD, take a blank CD, and burn the tracks to the blank
CD.  This is very handy for copying an audio CD that does not have CD Text,
since you can add it yourself.

But in k3b 1.0.1, when you follow those steps and then click Burn, the burn
dialog says "Please insert an empty CD-R(W) medium..." in the "Burn medium"
area.  The only way it will proceed is if you choose "Only create image", but
that would mean that you'd have to then take the image that was created and
burn it in a separate step.
Comment 1 Sebastian Trueg 2007-05-02 14:39:56 UTC
this is actually stupid. Damn. The first drawback of the new media system. I 
will see if I can find a solution.
Comment 2 markuss 2010-03-16 16:01:48 UTC
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.