Bug 147527 - Erasing the last session of a CD-RW erases more than the last session
Summary: Erasing the last session of a CD-RW erases more than the last session
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-07-04 09:13 UTC by Francois Marier
Modified: 2010-03-16 16:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Output (stderr) of erasing the last session (8.70 KB, text/plain)
2007-07-04 09:14 UTC, Francois Marier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Marier 2007-07-04 09:13:48 UTC
Version:           1.0.2 (using KDE KDE 3.5.7)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Jiří Paleček <jpalecek@web.de> also reported this problem with the CD-RW erasing on the Debian bug tracker (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413832):

"I tried to erase last session of a CD-RW with three sessions, but when the  
blanking was over, only the first session remaind on the CD."

That was with version 0.12.17, but then he got the same thing on K3b 1.0.2:

"I could reproduce the problem with version 1.0.2 too. I selected 'Erase  
last session' and it erased the last two. In the attached file, you can find stderr  
output of k3b, from which you should see what was happening."

I have attached the log he included to his bug report.
Comment 1 Francois Marier 2007-07-04 09:14:39 UTC
Created attachment 21034 [details]
Output (stderr) of erasing the last session
Comment 2 Sebastian Trueg 2007-07-18 17:02:00 UTC
actually all k3b does here it calling cdrecord. So in the end it is either a cdrecord bug or I misnamed the blanking parameters.
Comment 3 markuss 2010-03-16 16:02:27 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.