Summary: | intermittent verification failure with video DVDs | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Francois Marier <francois> |
Component: | Verfication | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Francois Marier
2007-08-01 06:16:31 UTC
Gary added the following comment: last week I installed the k3b version from sid and I can confirm that I am having the same problems. - k3b sometimes hangs on the verify stage when burning DVDs - whether ISO or as a project. When this happens, k3b cannot be shut down and must be killed. - k3b sometimes turns off DMA on the DVD device. - (I don't think I mentioned this before but) k3b sometimes hangs around as a zombie, preventing it from being launched until the existing instance is killed. I've had this problem for a couple months or so. The drive used to open at the end of writing, then close and run the verification. This was on my "server" system with a Optiarch DVD/CD writer. On my laptop, which does not have a motorized tray, the tray would eject, then a dialog would pop up saying, "Please insert the media to be verified" or "Cannot reload media, please check" (it's been a while, hard to remember), and an "load/abort/retry" selection. For the last month, the drives reach 50%, eject, and then never retract. The laptop does not get a "Cannot reload media" dialog, and if I do close the drive(s), they just sit there doing nothing until I cancel the write operation. So far, all the disks have been correctly written (or at least all the files I've checked). Debian Sid. Confirmed on Debian sid (k3b 1.0.4-7) when burning data DVD. When verification is required: - burning goes normally - dvd is ejected - k3b consumes 100% CPU, k3b windows is not refreshed - Need to kill k3b - can successfully verify DVD with md5sum HTH *** This bug has been marked as a duplicate of bug 156684 *** |