By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 522 - K3B has issue verifying burn
Summary: K3B has issue verifying burn
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: non-core programs (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: amd64 All
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-09-26 10:58 CDT by Kris
Modified: 2018-05-27 11:11 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2011-09-26 10:58:29 CDT 
When I burn a CD, I always tell K3B to verify. A bug that was in older versions of K3B (1.0.4 and earlier) is that they would eject the CD, then attempt to verify before I could push the tray back in (it's a laptop-style drive that can't re-insert the tray on it's own), then would fail the burning process because the CD wasn't present. On regular KDE 3.5.10 with K3B 1.0.5, this bug was fixed and K3B would display a dialog asking me to reinsert the drive before attempting to verify.

This bug seems to have been reintroduced on TDE 2.5.12 running K3B 1.0.5, the same version of K3B that was supposed to fix the bug. It is not constant, though -- most of the time, it attempts to verify before it has the CD back, and sometimes it display the dialog asking for the CD back.

I suspect it might be related somehow to the size of the ISO file, I just tried to burn a relatively small ISO (< 200MB), and most of the ISOs I burn are large (> 500MB) where the bug seems most prominent. I cannot verify for sure that it is size-related, I'd have to do some testing first and I just don't have the time for that at the moment.

Steps to reproduce:
1. Insert a blank CD or DVD into your CD burner. If you want to erase the CD or DVD first, use a good condition disc and do a full erase so there isn't any remaining data to interfere with the test.
2. Launch K3B.
3. Select an ISO to burn.
4. Make sure it is set to verify.
5. I always use the slowest burning speed available. I don't think this will have an effect on the bug, however.
6. Allow the burn to go through.
7. Sometimes it will fail the burn, sometimes it will display the dialog box.

System info:
Debian GNU/Linux 6.0.1a (don't have another distro to test on, nor the time to install another)
Kernel 2.6.39 from Debian Backports
Debian Backports enabled, system fully up-to-date
DVD +/- RW drive, support CD-RWs as well

Additional Info:
The last successful verify by both K3B and myself was about half an hour before my hard disk overheated (first time my hard disk overheated, I was able to verify because I created the ISO used out of files I wanted to back up using mkisofs).
Comment 1 Darrell 2013-05-22 21:31:23 CDT 
This bug exists in GIT (2013-05-22) in Slackware 14.0.

I tried burning a 2.8 GB data DVD. The burn is successful but not the verification.

When enabling "Verify written data," the tray ejects automatically at the (Overall progress) 50% progress marker, but after the tray closes the verification process halts immediately with an Error and the tray reopens.

Text in stdout/stderr that might be related:

(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed. I see that message three times.

Another possible error message:

TQGDict::hashKeyString: Invalid null key

That the process halts immediately after the tray closes is peculiar. By "immediate" I am implying the operating system does not yet have time to read the disk, let alone Trinity/K3B.

Conversely, I had no problem verifying a full CD ISO image. I noticed in the intermittent dialog that appears while the system and K3B reinitialize after ejecting/closing the tray, that some of the characters did not display correctly. Some kind of UTF problem?
Comment 2 Kris 2013-05-22 22:27:36 CDT 
(In reply to comment #1)
> This bug exists in GIT (2013-05-22) in Slackware 14.0.
> 
> I tried burning a 2.8 GB data DVD. The burn is successful but not the
> verification.
> 
> When enabling "Verify written data," the tray ejects automatically at the
> (Overall progress) 50% progress marker, but after the tray closes the
> verification process halts immediately with an Error and the tray reopens.
> 
> Text in stdout/stderr that might be related:
> 
> (K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed. I see that
> message three times.
> 
> Another possible error message:
> 
> TQGDict::hashKeyString: Invalid null key
> 
> That the process halts immediately after the tray closes is peculiar. By
> "immediate" I am implying the operating system does not yet have time to read
> the disk, let alone Trinity/K3B.
> 
> Conversely, I had no problem verifying a full CD ISO image. I noticed in the
> intermittent dialog that appears while the system and K3B reinitialize after
> ejecting/closing the tray, that some of the characters did not display
> correctly. Some kind of UTF problem?

Minus having incorrect characters in the dialog, I too have no issues with CDs, only with the DVDs. This tests true on both 3.5.13-sru and R14.

I will check for those error messages next time I burn DVDs.
Comment 3 Darrell 2013-05-22 22:52:54 CDT 
I think I found the problem with the goofy characters in the dialog. I'm searching through the commits to see whether there was a reason for the changes.
Comment 4 Darrell 2013-05-23 00:26:23 CDT 
Goofy characters fixed in commit e8fb3858.
Comment 5 Kris 2013-05-23 17:10:38 CDT 
(In reply to comment #2)
> (In reply to comment #1)
> > This bug exists in GIT (2013-05-22) in Slackware 14.0.
> > 
> > I tried burning a 2.8 GB data DVD. The burn is successful but not the
> > verification.
<snip>

An added note: from personal testing, it doesn't seem to matter the distro (I've tested in Debian Squeeze & Wheezy and Arch), nor the size of the DVD. I have had this happen on a 4.4GB DVD.
Comment 6 Darrell 2013-05-23 17:43:38 CDT 
Hopefully a clue that the verification fails the instant the tray closes. I'll guess the problem is k3b tries to start verifying the instant the tray closes rather than wait for the system to reinitialize and that causes the failure. Odd the same behavior does not occur with a CD. With a CD the dialog appears requesting a disk but the dialog disappears automatically after the system and k3b reinitialize.
Comment 7 Kris 2013-05-23 18:39:23 CDT 
(In reply to comment #6)
> Hopefully a clue that the verification fails the instant the tray closes. I'll
<snip>

For me, it fails *before* I can close the tray, on two separate laptops (neither one has a motorized tray). This would suggest (at least to me) that the failure occurs when the eject signal is sent to the drive, not when it closes.
Comment 8 Darrell 2013-05-23 18:43:24 CDT 
I found a work-around: In Settings->Configure K3b->Advanced, Enable/check "Do not eject medium after write process."

There remains a bug when the user ejects the disk after the burn because k3b is not waiting correctly for the system to reinitialize.

I wish I knew C++ better, but looks like the code for waiting is in /libk3b/jobs/k3biso9660imagewritingjob.cpp:268.