Bug 289691

Summary: Linux Mint 12, 64-bit (Ubuntu) -- Error in burning a CD with video files
Product: [Applications] k3b Reporter: Anthony Herbst <xpendx>
Component: Video CD projectAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: normal CC: chris, hugh+kdebug, trueg
Priority: NOR    
Version: 2.0.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Anthony Herbst 2011-12-23 19:26:04 UTC 
Version:           2.0.2
OS:                Linux

mkisofs returned an unknown error (code 2)
please send me an e-mail with the last output.


Devices
-----------------------
ATAPI DVD A  DH24AAS BP5P (/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]
Digital Video 1.10 (/dev/sr1, CD-ROM) [Error] [None] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 189371 (387831808 bytes)

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.7.3 (4.7.3)
QT Version:  4.7.4
Kernel:      3.0.0-13-generic

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

cdrecord
-----------------------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
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: 3 = CD-ROM XA mode 2
Driveropts: 'burnfree'
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   :
Vendor_info    : 'ATAPI   '
Identification : 'DVD A  DH24AAS  '
Revision       : 'BP5P'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1275648 = 1245 KB
FIFO size      : 12582912 = 12288 KB
Speed set to 8468 KB/s
Track 01: data   369 MB       
Total size:      424 MB (42:04.97) = 189373 sectors
Lout start:      425 MB (42:06/73) = 189373 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 170473
Forcespeed is OFF.
Starting to write CD/DVD at speed  48.0 in real TAO 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...
Starting new track at sector: 0
Track 01:    0 of  369 MB written.
Track 01:    1 of  369 MB written (fifo 100%) [buf 100%]   2.5x.
Track 01:    2 of  369 MB written (fifo 100%) [buf 100%]  21.8x.
Track 01:    3 of  369 MB written (fifo 100%) [buf 100%]  22.5x.
--- etc. for a hundred or more lines
32.48% done, estimate finish Fri Dec 23 12:05:53 2011
 32.74% done, estimate finish Fri Dec 23 12:05:52 2011
 33.01% done, estimate finish Fri Dec 23 12:05:51 2011
 33.27% done, estimate finish Fri Dec 23 12:05:50 2011
/usr/bin/genisoimage: No such file or directory. cannot open '/media/DV_/DCIM/100MEDIA/CLIP0001.MP4'

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid K3b data project -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-anther/k3buo6357.tmp -rational-rock -hide-list /tmp/kde-anther/k3btj6357.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-anther/k3bBE6357.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-anther/k3bkR6357.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid K3b data project -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-anther/k3bNh6357.tmp -rational-rock -hide-list /tmp/kde-anther/k3bse6357.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-anther/k3bKS6357.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-anther/k3bDj6357.tmp


Reproducible: Didn't try

Steps to Reproduce:
Try again to burn CD

Actual Results:  
Will try again

Expected Results:  
Not done yet

OS: Linux (x86_64) release 3.0.0-13-generic
Compiler: gcc
Comment 1 D. Hugh Redelmeier 2013-07-08 02:48:48 UTC 
What did K3b tell you was the problem?

In the debugging output, this line appears to be the important one:
/usr/bin/genisoimage: No such file or directory. cannot open '/media/DV_/DCIM/100MEDIA/CLIP0001.MP4'

genisoimage is saying that it cannot read this file, one that you've asked it to copy to the CD.

Why can it not read the file?  Does the file exist?  At exactly that path?  Right now?  Can it be read by genisoimage (for example, taking into account any SetGID or SetUID bit)?

I hope K3b's complaint matched what I'm guessing is the real problem.
Comment 2 Andrew Crouthamel 2018-11-12 02:51:47 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:57 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 Justin Zobel 2023-01-13 01:36:13 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 5 Bug Janitor Service 2023-01-28 05:08:11 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 6 Bug Janitor Service 2023-02-12 03:50:13 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!