Bug 137290 - Fails to extract an ISO image from a DVD
Summary: Fails to extract an ISO image from a DVD
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-13 17:54 UTC by Francois Marier
Modified: 2006-11-14 09:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Marier 2006-11-13 17:54:50 UTC
Version:           0.12.17 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I suspect this could be a hardware error, but since it apparently work in gnomebaker (which probably uses the same underlying tools), I'm not 100% sure.  Perhaps you would have ideas about what the user could test.

Here's the bug description as it was reported by Ramiro Aceves <ea1abz@gmail.com> on the Debian bug tracker (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398203):

K3B fails extracting an ISO image from DVD-RW media

Tools --> Copy DVD
Options --> Only create image
Image --> Write image file to /home/ramiro/test.iso
Start

Checking source media...

After some time:

Writing image file to /home/ramiro/test.iso
Reading with sector size 2048
Successfully read source DVD

That is wrong, resulting image "test.iso" is a very small file:

debian-etch:/home/ramiro# ls -l test.iso
-rw-r--r-- 1 ramiro ramiro 2048 2006-11-12 13:05 test.iso
debian-etch:/home/ramiro#

Syslog output shows DMA disabling on the DVD drive:

Nov 12 10:29:09 debian-etch kernel: hdb: irq timeout: status=0xd0 { Busy
}
Nov 12 10:29:09 debian-etch kernel: ide: failed opcode was: unknown
Nov 12 10:29:09 debian-etch kernel: hdb: DMA disabled
Nov 12 10:29:09 debian-etch kernel: hdb: ATAPI reset complete


K3b output:

************************************
System
-----------------------
K3b Version: 0.12.17

KDE Version: 3.5.5
QT Version:  3.3.7
Kernel:      2.6.17-2-686
Devices
-----------------------
TSSTcorp CD/DVDW TS-L632B TI33 (/dev/hdb, ) at /media/cdrom0 [CD-R;
CD-RW; CD-ROM; DVD-ROM; DVD-RAM; DVD-R; DVD-RW; DVD+R; DVD+RW; DVD+R DL]
[DVD-ROM; DVD-R Sequential; DVD-RAM; DVD-RW Restricted Overwrite; DVD-RW
Sequential; DVD+RW; DVD+R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW]
[SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R96R; Restricted Overwrite]

*************************************

Repeating the procedure with DMA disabled does not work.

Perhaps it is a hardware related problem. I have tested several DVD 
media types and brands that I have here, having some random result:

DVD-ROM VIDEO = OK
DVD-ROM DATA = OK
DVD-RW DATA = FAILED, FAILED, FAILED
DVD+RW  DATA=OK, OK
DVD-R DATA = OK, FAILED

Gnomebaker reads all media types correctly.
Comment 1 Sebastian Trueg 2006-11-13 18:04:38 UTC
Actually K3b does not use readcd (which is what gnomebaker uses) for this. It 
has its own implementation. But that is not the problem. The problem is most 
likely that K3b reads the Table of contents of the DVD wrong. Could you 
please try 1.0pre2 or even better the current svn trunk? Or yuo wait for 
1.0beta1 which will be released within this week.
Comment 2 Ramiro Aceves 2006-11-14 00:12:11 UTC
Dear Sebastian,

Yes!

I have just compiled and tested k3b-1.0pre2.tar.bz2 and it works just fine! 
Congratulations!
Thank you very much for your help.

Ramiro Aceves
System
-----------------------
K3b Version: 1.0pre2

KDE Version: 3.5.5
QT Version:  3.3.7
Kernel:      2.6.17-2-686
Devices
-----------------------
TSSTcorp CD/DVDW TS-L632B TI33 (/dev/hdb, ) at /media/cdrom0 [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R96R, Restricted Overwrite]
Comment 3 Sebastian Trueg 2006-11-14 09:27:43 UTC
*** Bug has been marked as fixed ***.