Bug 275874

Summary: cdrecord fails with error 254 when attempting to burn iso to CDR.
Product: [Applications] k3b Reporter: marks
Component: Image FormatsAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: normal CC: l_epa_m_inonda, trueg
Priority: NOR    
Version: 2.0.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Debug report from last failure
Debug output of k3b after fail writing dvd+r dl

Description marks 2011-06-17 06:44:01 UTC
Created attachment 61072 [details]
Debug report from last failure

Version:           2.0.2 (using KDE 4.6.2) 
OS:                Linux

cdrecord fails with error 254 when attempting to burn iso to CDR.
ruins media in process.

Was able to burn directory to DVD+RW.  Have not tried DVD-+R or RW CD yet.

Reproducible: Always

Steps to Reproduce:
Select "More Actions" then "Burn Image".
Select iso file.
Have tried changing speed, TAO, and has same problem even when simulated.

Actual Results:  
Starts to write then fails with error 254.

Expected Results:  
Successful write.

OS: Linux (x86_64) release 2.6.38-8-generic
Compiler: cc
Comment 1 mum 2011-11-17 14:14:53 UTC
Me too.

System reports:

Impossible finding cdrecord
K3b uses cdrecord for writing CD.
Solution: Install package cdrtools, in which is cdrecord.

---

But in that package cdrecord no more exists. It's now a symlink to wodim!
Comment 2 mum 2011-11-17 14:40:16 UTC
Created attachment 65783 [details]
Debug output of k3b after fail writing dvd+r dl

So Problem is for every kind of writing, not only for cdr.
Comment 3 Andrew Crouthamel 2018-11-12 02:52:35 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:32:48 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-08 22:45:01 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-23 05:04:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-07 03:55:02 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!