version is 2.0.2 (I am in the process of burning the latest Debian DVDs for an upgrade) Checksum comparison seems a rather dubious way of verifying a burn and gains you nothing in performance: chrisw@acer-Aspire-5610:~$ time cat /dev/sr0 >/dev/null real 8m51.207s user 0m0.128s sys 0m10.596s chrisw@acer-Aspire-5610:~$ time md5sum /dev/sr0 9c8951b69992c0a14821da030f27198d /dev/sr0 real 8m49.449s user 0m29.040s sys 0m9.092s chrisw@acer-Aspire-5610:~$ time cmp /dev/sr0 '/work/Debian 9.1.0/firmware-9.1.0-i386-DVD-1.iso' real 8m49.058s user 0m32.916s sys 0m20.336s chrisw@acer-Aspire-5610:~$ Checksum(s) can still be calculated, but, I think it's important to do a proper read back check. A graph of the read speed would also be helpful in showing if the burned disc has any bad spots.
Hi zcw913, v2.0.2 was not be maintained any more, please use K3b v17.08 https://github.com/KDE/k3b Regards, Leslie Zhai
You've got some problems wrt to what you've got on K3B on the internet: 1) the first thing I did before submitting the bug report was to search for a newer version but the search didn't show anything newer than 2.0.2 2) I also did a search in the bugs database and there didn't seem to be anything related 3) Today I was able to look at your message and discover that there are newer versions of K3B, BUT, there don't seem to be any release notes to be found for these newer versions except 17.11.0 and these didn't say anything about read back checks and checksums. 4) I downloaded 17.08 and there was a ChangeLog (good), but, there was nothing about read back checks (bad). I figured I'd try to build it to see what happens - haven't tried building anything with cmake before. I was in Mint and there is a Mint specific cmake and it seemed to install OK, but, it claimed my C compiler was defective. I switched to Debian which is where I want this to be anyway. Again, needed to install cmake, but, it was on the Debian DVD and it installed OK. No complaints about the C compiler this time, but, it also wanted C++. Fair enough, easy to install. Then it wanted Qt 5 - that was something like 60 packages and it took 2 attempts because the software manager is defective. Build still fails because it's just not the right version of Qt 5. I've got Debian 8.6.0 installed and would like to move to 9.1.0, but, it just won't install (I think they've gone to 9.2.0 in the time I've spent trying to install it). And if/when I get Debian 9 installed there's no guarantee that things will work any better. 5) Searched for Debian K3B packages today and got 2.0.2 for Debian 8 and 2.0.3 for Debian 9 which raises the question of what's compatible. What use can a version like 17.08 or the latest version, 17.11, be if it isn't compatible with something like the latest version of Debian? And, of course, there's no sign of any change in the read back check anyway. 6) Documentation for K3B on the internet seems to be for 2.0.2 and I think maybe earlier versions. I don't recall seeing any newer docs. Your refusal to accept a bug report for 2.0.2 basically boils down to a cop out. I, like most people, can't build my own Linux distribution or large chunks of it and have to depend on what others have built. Debian is a major Linux distribution and, at the moment, the latest working version appears to be 8. Bug reporting can't work if I can't report on what I can realistically actually have. __ Christopher Witkowski zcw913@aserty.com ----- Original Message ----- From: "Leslie Zhai" <bugzilla_noreply@kde.org> To: <zcw913@aserty.com> Sent: Thursday, October 12, 2017 11:02 PM Subject: [k3b] [Bug 385635] verification appears to be via checksum comparison rather than actual data comparison https://bugs.kde.org/show_bug.cgi?id=385635 Leslie Zhai <lesliezhai@llvm.org.cn> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lesliezhai@llvm.org.cn --- Comment #1 from Leslie Zhai <lesliezhai@llvm.org.cn> --- Hi zcw913, v2.0.2 was not be maintained any more, please use K3b v17.08 https://github.com/KDE/k3b Regards, Leslie Zhai
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!