Summary: | Verification after burning did not start (DVD) | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | artnorm |
Component: | general | Assignee: | Sebastian Trueg <trueg> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hjbecker, rickard.narstrom |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot of the process dialog in time the error occured |
Description
artnorm
2007-07-18 09:58:18 UTC
Today I encountered the same problem. What might help: This is a Laptop PC. The Disc is ejected and won't come back into the computer "on its own". If the CD-Lid is put in again, KDE starts to ask questions what to do with the Media. Works here on a laptop with K3b 1.0.3 which I will release hopefully today. Please test it once I did release it and close the bug if it works for you, too. Just sitting here with 1.0.3, having toasted a multisession dvd+rw and face this ort of problem: trap opened, closed again, verification doesn't start. With <=1.0.2 I did not have this problem. Weird. Btw.: When pressing cancel, K3B prints "burn process cancelled" in it's small log window, while it was successful and only the verification process was cancelled. And process status was Sl, so I couldn't exit K3B, but had to terminate it. > With <=1.0.2 I did not have this problem. Weird.
1.0.1 works, too?
sure about that?
I need some help here because I was never able to duplicate any of the verification problems. It always works here in all situations. with all versions of K3b.... > 1.0.1 works, too?
> sure about that?
Sure, I did burn and verified some dvd+rw sessions with this version as well as 1.0.2. Never used K3B 1.0.0, though.
I'll see to try to gather more information, next time I'll toast something.
Created attachment 21633 [details]
Screenshot of the process dialog in time the error occured
Sorry for not being able to give feedback earlier. I now could made a test with
K3b 1.0.3 within the laptop again I encountered the problems with. This Time I
got an Errormessage, you can see it in the picture. I paste the Log which
sized for a better view, it does not contain the message as far I can see:
System
-----------------------
K3b Version: 1.0.3
KDE Version: 3.5.6
QT Version: 3.3.7
Kernel: 2.6.20-16-generic
Devices
-----------------------
MATSHITA DVD-RAM UJ-850 RB01 (/dev/scd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM,
DVD-R, DVD-RW, DVD-R doppelschichtig, DVD+R, DVD+RW, DVD+R doppelschichtig]
[DVD-ROM, DVD-R Sequentiell, Zweischichtige DVD-R Sequentiell,
Zweischicht-DVD-R Sprung, DVD-Ram, DVD-RW Eingeschränktes Überbrennen, DVD-RW
Sequentiell, DVD+RW, DVD+R, Zweischichtige DVD+R, CD-ROM, CD-R, CD-RW] [SAO,
TAO, Eingeschränktes Überschreiben, Sprung zwischen DVD-Schichten]
Burned media
-----------------------
DVD-R Sequentiell
K3bIsoImager
-----------------------
mkisofs print size result: 544649 (1115441152 bytes)
Pipe throughput: 1115441152 bytes read, 1115441152 bytes written.
Used versions
-----------------------
mkisofs: 1.1.2
growisofs: 7.0.1
growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/scd0 obs=32k seek=0'
/dev/scd0: "Current Write Speed" is 8.2x1352KBps.
0/1115441152 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
[...]
1096318976/1115441152 (98.3%) @4.9x, remaining 0:03 RBU 57.0% UBU 93.9%
/dev/scd0: flushing cache
/dev/scd0: updating RMA
/dev/scd0: closing session
growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/scd0=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=tracksize:544649 -speed=8 -overburn
-use-the-force-luke=bufsize:32m
mkisofs
-----------------------
544649
I: -input-charset not specified, using utf-8 (detected in locale settings)
0.09% done, estimate finish Sat Sep 15 19:49:10 2007
[...]
99.88% done, estimate finish Sat Sep 15 19:53:04 2007
Total translation table size: 0
Total rockridge attributes bytes: 19718
Total directory bytes: 53730
Path table size(bytes): 306
Max brk space used 20000
544649 extents written (1063 MB)
mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid Kontrastfilm
Offline Version -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN
TRUEG AND THE K3B TEAM -publisher -preparer -sysid LINUX -volset-size 1
-volset-seqno 1 -sort /tmp/kde-mot/k3bXU7cpb.tmp -rational-rock -hide-list
/tmp/kde-mot/k3bR5LMUa.tmp -joliet -joliet-long -hide-joliet-list
/tmp/kde-mot/k3bXZ9ntb.tmp -no-cache-inodes -full-iso9660-filenames -iso-level
2 -path-list /tmp/kde-mot/k3b1jv4Za.tmp
mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid Kontrastfilm Offline Version
-volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B
TEAM -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort
/tmp/kde-mot/k3bhd1dlc.tmp -rational-rock -hide-list /tmp/kde-mot/k3bhVXoDb.tmp
-joliet -joliet-long -hide-joliet-list /tmp/kde-mot/k3bvCAabc.tmp
-no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list
/tmp/kde-mot/k3b3r5z6b.tmp
I experience the same in k3b 1.0.4. I have a slot-loading drive (one that can not close automatic). In the previous version of k3b (0.12.17), I got a popup message asking me to close the tray, where I would OK, and then the verification would start. Is there any progress in this bug? Isn't it possible to start the verification manually? A Button could be added to the dialog-window "manual verify" or similar. For a better Feedback, the Drives state could be displayed (closed, opened, initialising, burning, reading - whatever). Additionally, the state of K3B could be displayed as well: burning, ejecting, waiting for the drive to come in again, verifying and similar as the author better knows what K3B is doing at that point. I encounetered the same problem on my version 1.0.3. I'll try and translate the messages in English, as my local language is Afrikaans. I checked for the "Verify disc after writing" option. After the DVD was burned, it displays the message "The disc finish successfully" and the next message is "DVD disc 1 was successfully written". The next step is then to verify the disc and this is where it sometimes get frozen up. The total progress shows at 66%, and it shows that it is busy verifying the media at 0%, 4400 of 4400 MB. When I click on the Cancel button, the application froze up altogether and I have to kill the application. I have a feeling it could be the DVD disc itself that is bad, as I have experienced before even with Nero on Windows XP, but the application should not stop responding if this is the case. I don't know whether the fact that I am using Compiz Fusion has something to do with it, because this problem surfaced after I have installed Compiz. I forgot to mention that my DVD was burned only halfway through, according to the burn marks physicaly made on the DVD. Sebastian, can you offer an additional "verify DVD" command inside the UI or menu? Then users who know their passive/slimine cd-tray has problems with verifying can trigger it on their own afterwards. Then even if this bug still exists, the user will be able to help herself. Hi. I've experienced the same problem today. I'm using k3b 1.0.4 on a laptop which's drive can not be pulled in automatically. The burning process stopped at 50% and never finished correctly, i.e. same behaviour as described above. Here's a little workaround that has helped in my case: There's an option in the configuration dialog (under "advanced"): "Do not eject medium after write process". After enabling the option the write process and verification process worked as expected. (Sure, the medium wasn't ejected at the end, but that's not as bad as no working verification ;-)) So, at least in this case, the solution would be: only eject drive after verifiction, not before. Has this additional eject/reload cycle between writing/verifing been added because some burners aren't accessable after successful write process? If yes, if it is somehow possible to determine that from the drive's information (firmware?) it would be great k3b would adept it's behaviour. Or at least offers an option so the behaviour can be changed by the user :-) (Oh btw. i've burned multisssion. I don't know how my burner behaves after actually finishing (closing) a dvd :-/ ) *** This bug has been marked as a duplicate of 156684 *** |