Red Hat Bugzilla – Bug 1249195
k3b computes wrongly the initial size
Last modified: 2016-11-30 19:35:46 EST
Description of problem:
When attempting to write a BluRay Disc, k3b reports initially that are still > 40 MB available on disc. At the end of the writing, it fails to complete the writing and it reports that capacity is exceeded by > 200 MB. This of course results in a toasted BD.
Version-Release number of selected component (if applicable):
at least once
Steps to Reproduce:
1.follow steps from the description
media is successfully written
maybe the LEad-Out size is not computed? The failure occured when the disc was supposed to be closed. Attempting to manually fix it with wodim fails.
Problem seems to be solved (together with my burning errors on my newer bluray writer drive) by replacing cdrkit tools with those from:
Unfortunately, we cannot ship cdrtools for licensing reasons:
Are you sure K3b was using wodim? Wodim does not support BluRay, at least it is not documented to support it. K3b should be using growisofs from the dvd+rw-tools package, which does support BluRay. Your issue sounds like a bug in growisofs.
K3b should probably be using libburn from http://libburnia-project.org/ , which is the only burning project without licensing issues that is actually actively maintained. (Both cdrkit/wodim and dvd+rw-tools/growisofs are abandoned, sadly.) Making it work with cdrskin should be fairly easy, it should just get support for detecting it so that it can turn off the workarounds for cdrecord/wodim bugs when cdrskin is detected. In the long-term, it should really link the library and stop shelling out to an external process entirely.
See also: https://bugs.kde.org/show_bug.cgi?id=137436
The problem is mainly that K3b's upstream maintenance state is also not good, which explains its reliance on obsolete burning tools.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.