Bug 180043

Summary:	Internal Error: Verification job improperly initilized
Product:	[Applications] k3b	Reporter:	Elmar Stellnberger (AT/K) <estellnb>
Component:	general	Assignee:	Sebastian Trueg <trueg>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	1.0.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Internal Error: Verification job improperly initilized (specified track number not found on medium) k3b 1.0.5, using KDE 3.5.10

Description Elmar Stellnberger (AT/K) 2009-01-08 17:46:11 UTC

Version:           1.0.4 (using 3.5.10 "release 33.1" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.25.18-0.2-xen

  After burning the new freebsd-i386.iso K3B has refused to verify the data which has just had been burned:
Internal Error: Verification job improperly initilized
  Verification is important because a just burnt image sometimes in deed turns out not to burned free of errors.

Comment 1 Elmar Stellnberger (AT/K) 2009-01-08 17:47:19 UTC

Created attachment 30033 [details]
Internal Error: Verification job improperly initilized (specified track number not found on medium)

Comment 2 Elmar Stellnberger (AT/K) 2009-02-22 12:39:42 UTC

Created attachment 31538 [details]
k3b 1.0.5, using KDE 3.5.10

Comment 3 Elmar Stellnberger (AT/K) 2009-03-25 18:10:39 UTC

Has now worked again for my last burns. Wanna mark this as fixed but reopen if error occurrs again (k3b-1.0.5-48.22).
Qt: 3.3.8b
KDE: 3.5.10 "release 21.11"
K3b: 1.0.5

Comment 4 Elmar Stellnberger (AT/K) 2009-03-30 22:34:03 UTC

  Now it does not print 'verification job improperly initilized' any more, but even worse the verification will fail even if the disk had been burnt correctly! I have tested this by reading in and comparing the read in with the previously burnt image manually; that after verification has failed several times on different burnt CDs.
  Please fix this as soon as possible because otherwise many well burnt CDs will be dumped unduely!!

Comment 5 markuss 2010-03-16 16:12:16 UTC

In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.