Bug 137402

Summary:	K3b should remember the calculated MD5 sum
Product:	[Applications] k3b	Reporter:	Francois Marier <francois>
Component:	general	Assignee:	Sebastian Trueg <trueg>
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	VLO
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Francois Marier 2006-11-15 17:45:10 UTC

Version:           0.12.17 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Here is a suggestion from Thue Janus Kristensen <thuejk@gmail.com> as reported on the Debian bug tracker (http://bugs.debian.org/398795):

In the initial window, select an ISO image. A screen pops up, and it
starts calculating the image's MD5 sum.

If I start writing before the sum is calculated then it writes
"calculation failed" (should probably be "calculation cancelled").

I then burn the image, and as part of the burn verification the
image's MD5 sum is calculated. However, when I close that dialog after
finishing burning and come back to the previous screen it still says
"calculation failed". It could just as easily reuse the MD5 sum it had
just calculated. That would also be useful when burning severel DVDs
from the same image sequentially.

Comment 1 Christoph Burger-Scheidlin 2006-11-15 20:28:09 UTC

In my opinion this is a usability problem in that the MD5 sum of the image should not be displayed at all in the burn dialog since it does not serve a practical purpose (apart from being confusing in the sense that people think they have to wait for it to finish).

I am marking this as very low priority, since it will probably go away when bugs like bug 98128 and bug 116765 are implemented.

Apart from that it is a valid point

Comment 2 Sebastian Trueg 2006-11-16 09:56:13 UTC

I mark this one as fixed although K3b does not behave as requested. K3b calculates the md5sum while burning, so the effect it the same.

Comment 3 Thue Janus Kristensen 2006-11-16 21:04:41 UTC

It seems that it does not even use the MD5 sum calculated at the first screen, even if you wait for it to be calculated. That is just silly.

Comment 4 Sebastian Trueg 2006-11-18 13:57:17 UTC

no, it is not. There is no time lost the way K3b does it and it is much cleaner.