Bug 279245 - K3B repeats verification on the same DVD copy
Summary: K3B repeats verification on the same DVD copy
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: Verfication (show other bugs)
Version: 1.91.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 03:19 UTC by planck-kde
Modified: 2021-03-09 06:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description planck-kde 2011-08-03 03:19:51 UTC
Version:           1.91.0 (using KDE 4.4.5) 
OS:                Linux

When making multiple copies of a data DVD and verifying the copies, the N'th copy was completely verified N times.  That is, the 1st copy was verified once, the 2nd copy was verified twice, and so on.  These extra verifications did appear in the log.  I did not notice the problem until the 5th copy (of 7) as the amount of data on the DVD was only 900 MB, and it did not take very long per pass.

Reproducible: Always

Steps to Reproduce:
Select the "Copy Medium..." action, choosing a number of copies greater than 1, and enabling the "Verify written data" option. Tested with three source DVD+Rs holding different amounts of data.

Actual Results:  
In each case, the N'th copy was verified N times according to the log, and the verify step took longer for each successive copy.

Expected Results:  
Each successive copy should be verified only once, and take the same amount of time as the first copy.

DVD burner is an LG GSA-4163B
Writing medium was Imation branded DVD+R, with media ID "CMC MAG/M01"
Comment 1 Mauro Molinari 2014-11-29 16:54:43 UTC
I see the exact same behaviour in K3b 2.0.2.

Still unconfirmed since 2011? :-O
Comment 2 Justin Zobel 2021-03-09 06:28:22 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.