Bug 255279 - K3b will not accept an empty BD-R when burning image.
Summary: K3b will not accept an empty BD-R when burning image.
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Image Formats (show other bugs)
Version: 2.0.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-26 01:52 UTC by Eric
Modified: 2023-02-11 03:51 UTC (History)
2 users (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 Eric 2010-10-26 01:52:59 UTC
Version:           2.0.1
OS:                Linux

After creating a 19.1GB ISO file (with K3b), I tried burning it with "burn image".
The media was considered "Empty Error medium" by the software.


Reproducible: Always

Steps to Reproduce:
In "burn image" window, after selecting the iso image, the BD-R media is reported as "Empty Error medium". Replacing the media with another media, from a different brand resulted the same.
After the iso was mounted, a "data project" was selected and the files were burned to the same BD-R.
Eventually the regular burn failed as well (at the last 40MB), however a checksum to the files showed that all the files on the media are OK.




I've attached the debug information from the failed burn.
Comment 1 Andrew Crouthamel 2018-11-12 02:48:51 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 2 Andrew Crouthamel 2018-11-21 04:43:02 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 3 Justin Zobel 2023-01-12 01:57:56 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 4 Bug Janitor Service 2023-01-27 05:06:59 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 5 Bug Janitor Service 2023-02-11 03:51:53 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!