https://bugs.kde.org/show_bug.cgi?id=511549
Bug ID: 511549
Summary: K3b won't erase CD-RWs
Classification: Applications
Product: k3b
Version First 25.08.1
Reported In:
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Burning/Hardware
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
SUMMARY
K3b simply refuses to erase *any* of my CD-RWs. I have tried this with several
CD-RWs, one of which has only been written once, so it isn't a matter of too
many rewrites. I have done this many times before with no problems.
STEPS TO REPRODUCE
1. Insert an already burned CD-RW into drive
2. Setup a data project
3. Click on Burn
4. Confirm settings and start burning from the dialog box
5. K3b prompts that this CD-RW isn't empty and should be erased
6. Click erase
7. Erase instantly fails.
OBSERVED RESULT
K3b simply says erasing fails, and immediately ejects the CD-RW.
EXPECTED RESULT
K3b should erase the CD-RW, and then finish writing the project to the CD-RW.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-6-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
I have not tried this since my upgrade from Kubuntu 25.04 to Kubuntu 25.10.
Maybe this is a packaging or dependency issue? Will try in a Kubuntu 25.04 VM
later this week.
This log is shown when running K3b from the terminal:
Waiting for medium "complete medium, incomplete medium" "CD-RW" "Please insert
a rewritable CD medium into drive<p><b>ASUS BW-16D1HT (/dev/sr0)</b>."
"/dev/sr0"
finishWaiting()
***** "cdrecord" parameters:
"/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=10 -tao driveropts=burnfree
-force blank=fast"
"/dev/sr0"
started
( "cdrecord" ) "TOC Type: 1 = CD-ROM"
"/dev/sr0"
(K3b::CdrecordWriter) error: 11
starting command: "(CommandEject)"
Resetting medium in "/dev/sr0"
no medium found
finished command: "(CommandEject)"
--
You are receiving this mail because:
You are watching all bug changes.
