Version: 1.0.4 (using KDE KDE 3.5.7) Installed from: Fedora RPMs Compiler: gcc 4.1.2 rpm shipped with Fedora 7 OS: Linux After successfully burning a data dvd with "verify written data" option, the dvd is ejected but after that it isn't reloaded: the tray remains open. If I close the tray manually, the process hangs (the timer continues to run, but nothing happens). This happens with a NEC 3500AG and a LG 4163B - the previous version of K3b worked fine (apart from the "erasing failed" message after the pre-formatting step of dvd+rw burning).
sorry, I wasn't clear: KDE is installed via Fedora RPM; K3b is compiled from source with GCC 4.1.2
I have just the same trouble with the same version of K3b on Debian Sid (KDE 3.5.8). All official packages. DIsk is ejected, but remain out of the tray and verification doesn't start. Closing manually the tray is vain... MS
Exactly the same problem here. K3b 1.0.4 using KDE 3.5.8, Arch Linux, packages installed from Arch repositories.
Same as the message above (#3).
Same here on Linux from scratch system. Previous version worked okay.
confirmed.
*** Bug 152226 has been marked as a duplicate of this bug. ***
Created attachment 22403 [details] Patch to revert the change causing the regression I believe this regression is caused by this change: * Do only reload the medium before verification if necessary, i.e. if the newly written track cannot be read otherwise (many old drives depend on this). Hopefully this will at least work around the aweful "DMA disabled" bug for many users. (I can't imagine any of the other changes from 1.0.3 to 1.0.4 causing this, and this change looks very related.) Until Sebastian Trüg comes up with a real fix, here's a patch which reverts that change.
The patch works for me, thanks!
Sebastian, this bug is now over a month old, any comment/insights here?
confirmed on gentoo
confirmed on KDE 3.5.8, Kubuntu 7.10 (+backports), k3b 1.0.4, (2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux) This is on a Dell laptop. Burning finishes, ejects, then can only be cancelled.
fwiw, fedora is now including the patch (from comment #8) to revert the problematic code, at least until we get any upstream comment/feedback.
Someone else found that verification will work if k3b is set not to eject the medium after the write process has finished (Settings -> Advanced, Miscellaneous, Do not eject medium after write process). It works for me too.
*** Bug 157767 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 156684 ***
This patch doesn't solve the problem for me. If I don't prevent from ejecting the disk after the burn, the verification process doesn't start and ends with this error: "no track to verify".