Description of problem:
Previous versions of k3b automatically chose growisofs when writing a dual layer
DVD+R. The version releases with fedora 13 seems to always default to using
wodim for all writing, but unfortunately wodim doesn't seem to work on dual
layer DVD+R (at least not with the combination of media and drive I have).
I finally found the option in the burn dialog to select which program to use
and discovered that growisofs works perfectly with the same media and drive
where wodim always fails.
Since older k3b versions apparently chose growisofs automatically, this seems
like a regression.
Version-Release number of selected component (if applicable):
I burned 3 coasters trying different speeds and options till I found the
option to use growisofs. The failures were all the same, the write would
stop working at about 1 gig worth of data and give obscure errors messages
about having no permission to access device.
Steps to Reproduce:
1.use k3b with default options to write 8 gig to a DVD+R DL disk
2.watch it fail at about 1 gig.
backed up data I can verify against the originals.
The media I'm using is 8x TDK DVD+R DL (which is identified by k3b as actually
being ritek media).
The drive I'm using is a Pioneer DVR-117D
I always get the failure with the TDK media. I was able to write a Verbatim
DVD+R DL disk, but wodim decided for some reason that it has to write
at 2.4X rather than the 8X the Verbatim media is supposedly rated at.
Here's what dvd+rw-mediainfo has to say about the TDK media:
zooty> dvd+rw-mediainfo /dev/sr0
INQUIRY: [PIONEER ][DVD-RW DVR-117D][1.07]
GET [CURRENT] CONFIGURATION:
Mounted Media: 2Bh, DVD+R Double Layer
Media ID: RITEK/S04
Current Write Speed: 8.0x1385=11080KB/s
Write Speed #0: 8.0x1385=11080KB/s
Write Speed #1: 6.0x1385=8310KB/s
Write Speed #2: 4.0x1385=5540KB/s
Write Speed #3: 2.4x1385=3324KB/s
Speed Descriptor#0: 00/4173823 R@8.0x1385=11080KB/s W@8.0x1385=11080KB/s
Speed Descriptor#1: 00/4173823 R@6.0x1385=8310KB/s W@6.0x1385=8310KB/s
Speed Descriptor#2: 00/4173823 R@4.0x1385=5540KB/s W@4.0x1385=5540KB/s
Speed Descriptor#3: 00/4173823 R@2.4x1385=3324KB/s W@2.4x1385=3324KB/s
READ DVD STRUCTURE[#0h]:
Media Book Type: 00h, DVD-ROM book [revision 0]
Legacy lead-out at: 2086912*2KB=4273995776
DVD+R DOUBLE LAYER BOUNDARY INFORMATION:
L0 Data Zone Capacity: 2086912*2KB, can still be set
READ DISC INFORMATION:
Disc status: blank
Number of Sessions: 1
State of Last Session: empty
"Next" Track: 1
Number of Tracks: 1
READ TRACK INFORMATION[#1]:
Track State: blank
Track Start Address: 0*2KB
Next Writable Address: 0*2KB
Free Blocks: 4173824*2KB
Track Size: 4173824*2KB
ROM Compatibility LBA: 242432
READ CAPACITY: 0*2048=0
Looks like we can consider switching to using growisofs by default then. any objections?
As discussed on IRC: no objections from me, in fact I have been complaining about wodim getting used by default ever since I first noticed it (even though it did work for me). Wodim's DVD support is known to be bad, DVDs are what growisofs is for.
I've never tried growisofs on CDs. It might be just as bad as wodim is on
DVDs :-). The previous behavior of k3b was to select wodim for CDs and
growisofs for DVDs by default.
AFAIK, growisofs doesn't support CDs at all, only DVDs and BluRay discs.
K3b 1 always used cdrecord/wodim for CDs and growisofs for DVDs, it didn't even SUPPORT using wodim for DVDs. That feature was added by somebody using Jörg Schilling's new cdrecord with the built-in ProDVD code, but we (and wodim upstream) aren't shipping that code for licensing reasons (it's under the CDDL (previous versions were entirely proprietary, so we can't fork an old version either), other code it's linked to is GPLed, making the combination undistributable). What is shipped in wodim is an ancient experimental community-contributed DVD support patch for cdrecord (from the times where ProDVD was entirely proprietary). So it's a bad idea to use wodim for DVDs.
We're now evaluating a K3b patch where it will refuse to use cdrecord for DVDs if cdrecord is actually wodim, choosing growisofs instead. So far we're asking upstream for feedback, but chances are high it will land at least in our K3b builds, and hopefully upstream too.
k3b-2.0.2-2.fc14 has been submitted as an update for Fedora 14.
k3b-2.0.2-2.fc13 has been submitted as an update for Fedora 13.
k3b-2.0.2-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update k3b'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/k3b-2.0.2-2.fc14
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
k3b-2.0.2-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
k3b-2.0.2-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to comment #5)
> undistributable). What is shipped in wodim is an ancient experimental
> community-contributed DVD support patch for cdrecord (from the times where
> ProDVD was entirely proprietary). So it's a bad idea to use wodim for DVDs.
Why are you posting that link? I know that page all too well.
It is true that the wodim DVD support is of poor quality, and this is exactly why we now default K3b to growisofs.
However, unfortunately, Jörg Schilling's views of licensing are somewhat "original" and, in particular, not shared by Red Hat Legal. And the decisions of what is shippable in Fedora are taken by Red Hat Legal, not by Jörg Schilling. I also think a company's legal department is more likely to be right on legal questions than an individual developer.
This bug has also been resolved for 3 months, so your posting that link is of no help whatsoever.
Sorry, the bug has been resolved for 2 months, not 3 months. :-) But that doesn't make your comment any less off topic.
I'm running k3b-2.0.2-2.fc14.x86_64, and when I neglected to explicitly choose growisofs just the other day when attempting to backup about 7.9 gig of files to a double sided DVD+R disk, k3b once again decided to use wodim and generated another coaster, so the bug don't look resolved to me.
Make that dual layer, not double sided.
I'm using Fedora 14 and k3b-2.0.2-2.fc14.i686 and still uses wodim.
How can I change this setting to growisofs?
Don't know any way to make it stick permanently, but if you look close once you bring up the burn dialog there is a pull down menu for "burning app" which normally defaults to "auto", but you can change to explicitly select growisofs.
(Assuming you have growisofs installed).
Hi Tom, I dont see anything like "burning app" on burn dialog, just image type, burn medium, speed, writing mode, data mode, copies and others but not burning app.
Is there a way to change in settings / setup external programs?
Created attachment 488511 [details]
screenshot of burn dialog
Here's what I see when burning a data DVD. I guess it is called "Writing app", not "burning app". I've highlighted it in red in the screenshot.
Created attachment 488514 [details]
screenshot k3b 2.0.2-2.fc14.i686
Tom, this is mine, no option here.
Are you sure you are using 2.0.2-2?
Aparently using wodim with sudo works fine with just one error:
"session fixation error"
sudo wodim speed=3 -dao dev=/dev/sr1 file.iso
zooty> rpm -q k3b
Sure looks like it :-).
I also have this:
zooty> rpm -q -f /usr/bin/growisofs
which is where /usr/bin/growisofs comes from. Maybe you don't have that
installed, so k3b doesn't bother providing the choice? That's the only
thing I can think of.
Yes, I have the same:
Looks like in addition to k3bmetawriter.cpp, I also need to patch k3bdvdcopyjob.cpp and k3bdatajob.cpp, which for some reason have their own idea of the writing app to use.
This doesn't affect ISO burning (k3biso9660imagewritingjob.cpp delegates the choice of writing app to the MetaWriter), so if the patch was tested with ISO burning, that'd be why it passed testing.
k3b-2.0.2-4.fc15 has been submitted as an update for Fedora 15.
k3b-2.0.2-4.fc14 has been submitted as an update for Fedora 14.
k3b-2.0.2-4.fc13 has been submitted as an update for Fedora 13.
I submitted the patch upstream: https://git.reviewboard.kde.org/r/101208/
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing k3b-2.0.2-4.fc14'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
(In reply to comment #13)
> Why are you posting that link? I know that page all too well.
Because no one explains the real problems of cdrkit/wodim. That page does it.
You? How about other people ?
> However, unfortunately, Jörg Schilling's views of licensing are somewhat
> "original" and, in particular, not shared by Red Hat Legal. And the decisions
> of what is shippable in Fedora are taken by Red Hat Legal, not by Jörg
> Schilling. I also think a company's legal department is more likely to be right
> on legal questions than an individual developer.
Irrelevant, nobody talked about cdrecord.
I already explained the issue which is relevant to THIS bug (the fact that wodim is using the old experimental community DVD patch due to licensing conflicts with the new ProDVD code by Jörg Schilling) as completely and objectively as I could in the comment #5 you originally replied to. Posting that link to an already-closed bug report wasn't helpful. (The information in Tom Horsley's comment #15 that the bug wasn't fixed properly was helpful, though. This, too, should be fixed now.)
IMHO, wodim should just drop DVD support entirely, or maybe execv growisofs for it.
(In reply to comment #19)
> Hi Tom, I dont see anything like "burning app" on burn dialog, just image type,
> burn medium, speed, writing mode, data mode, copies and others but not burning
> Is there a way to change in settings / setup external programs?
Go to Settings -> Configure K3B -> Advanced and check the option "Show advanced GUI elements". Work for me :-)
So, has anybody tried the k3b-2.0.2-4.fc1 builds in updates-testing yet? They should be selecting growisofs automatically, without having to manually select it.
k3b-2.0.2-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
k3b-2.0.2-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
k3b-2.0.2-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.