Bug 317987 - Problem with data burning
Summary: Problem with data burning
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 2.0.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-07 18:46 UTC by Omar Bautista González
Modified: 2023-02-17 03:48 UTC (History)
2 users (show)

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 Omar Bautista González 2013-04-07 18:46:56 UTC
Sometimes when I try to burn a DVD, K3b can't do it.

Reproducible: Sometimes

Steps to Reproduce:
1. Load the DVD data to the project
2. Specify a speed of 4x
3. It tolds me to try a lower speed and then I try the 2.4x
Actual Results:  
Whe K3b try to burn the data it can't "maybe because it does not like the medium"

Expected Results:  
The burned data.

I use K3b to backup information. But I really don't know why this bug happen. This is the bug report of K3b:

Devices
-----------------------
HL-DT-ST DVDRAM GP08LU10 KE01 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, 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/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 1757592 (3599548416 bytes)

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.8.5 (4.8.5)
QT Version:  4.8.1
Kernel:      3.2.0-39-generic-pae

Used versions
-----------------------
mkisofs: 1.1.11
cdrecord: 1.1.11

cdrecord
-----------------------
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.11
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Driveropts: 'burnfree'
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identification : 'DVDRAM GP08LU10 '
Revision       : 'KE01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011 (DVD-R sequential recording)
Profile: 0x0012 (DVD-RAM) 
Profile: 0x0011 (DVD-R sequential recording) (current)
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0016 (DVD-R/DL layer jump recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x001A (DVD+RW) 
Profile: 0x001B (DVD+R) 
Profile: 0x002B (DVD+R/DL) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x0009 (CD-R) 
Profile: 0x000A (CD-RW) 
Profile: 0x0008 (CD-ROM) 
Profile: 0x0002 (Removable disk) 
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags   : SWABAUDIO BURNFREE 
Supported modes: PACKET SAO
Drive buf size : 1114112 = 1088 KB
Drive DMA Speed: 5838 kB/s 33x CD 4x DVD
FIFO size      : 12582912 = 12288 KB
Speed set to 5540 KB/s
Track 01: data  3432 MB        
Total size:     3942 MB (390:34.56) = 1757592 sectors
Lout start:     3942 MB (390:36/42) = 1757592 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 540904
Starting to write CD/DVD at speed   4.0 in real SAO mode for multi session.
Last chance to quit, starting real write in    2 seconds.
   1 seconds.
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
Starting new track at sector: 0
Track 01:    0 of 3432 MB written.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: cmd timeout after 200.334 (200) s
CDB:  2A 00 00 00 00 00 00 00 1F 00
resid: 59904
cmd finished after 200.334s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 0 bytes
Writing  time:  211.667s
Average write speed  12.7x.
Fixating...
Fixating time:    0.024s
/usr/bin/wodim: fifo had 192 puts and 1 gets.
/usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was 100%.

cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -sao driveropts=burnfree -multi -data -tsize=1757592s -

mkisofs
-----------------------
1757592
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.03% done, estimate finish Sun Apr  7 18:16:36 2013
  0.06% done, estimate finish Sun Apr  7 16:23:19 2013
  0.09% done, estimate finish Sun Apr  7 15:44:51 2013
  0.11% done, estimate finish Sun Apr  7 15:25:01 2013
  0.14% done, estimate finish Sun Apr  7 15:13:31 2013
  0.17% done, estimate finish Sun Apr  7 15:05:49 2013
  0.20% done, estimate finish Sun Apr  7 15:00:18 2013
  0.23% done, estimate finish Sun Apr  7 14:56:02 2013
  0.26% done, estimate finish Sun Apr  7 14:52:49 2013
  0.28% done, estimate finish Sun Apr  7 14:50:15 2013
  0.31% done, estimate finish Sun Apr  7 14:53:28 2013
  0.34% done, estimate finish Sun Apr  7 14:51:12 2013

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid DVD15 -volset  -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-omar/k3bD13383.tmp -rational-rock -hide-list /tmp/kde-omar/k3bz13383.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-omar/k3bB13383.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-omar/k3bm13383.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid DVD15 -volset  -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-omar/k3bZ13383.tmp -rational-rock -hide-list /tmp/kde-omar/k3br13383.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-omar/k3bW13383.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-omar/k3bw13383.tmp
Comment 1 joerg.schilling 2013-12-19 14:28:23 UTC
You are not using the original cdrtools, but something that is based on a version
from September 2004 with DVD-support removed and with Debian specific bugs
added.

I recommend you to upgrade to recent original cdrtools from ftp://ftp.berlios.de/pub/cdrecord/alpha/
Comment 2 Andrew Crouthamel 2018-11-12 02:48:27 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:47:08 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 joerg.schilling 2018-11-21 11:20:38 UTC
Please however be careful: Some unfriendly Linux distros still ship the
dead fork called "cdrkit" that results in a source state from May 2004.
So you should warn your users in case that old software has been installed.

Make sure to use a PATH that finds /opt/schily/bin/mkisofs before
/usr/bin/mkisofs and inform your users that recent software is at this
location:

Bi-weekly snapshots (recommended):
http://sourceforge.net/projects/schilytools/files/

Less frequent regular release:
http://sourceforge.net/projects/cdrtools/files/alpha

So called "stable" release:
http://sourceforge.net/projects/cdrtools/files/
Comment 5 Justin Zobel 2023-01-18 02:40:53 UTC
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!
Comment 6 Bug Janitor Service 2023-02-02 05:00:48 UTC
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!
Comment 7 Bug Janitor Service 2023-02-17 03:48:34 UTC
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!