Version: 2.0.0 OS: Linux Devices ----------------------- HL-DT-ST DVDRAM GH22NS50 TN02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R Çift Katman, DVD+R, DVD+RW, DVD+R Çift Katman) [DVD-ROM, DVD-R Sıralı, DVD-R Çift Katman Sıralı, DVD-R Çift Katman Atlama, DVD-RAM, DVD-RW Kısıtlanmış Üzerine Yazma, DVD-RW Sıralı, DVD+RW, DVD+R, DVD-R Çift Katman, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Sınırlandırılmış Yeniden Yazma, Katman Atlama (Layer Jump)] [%7] System ----------------------- K3b Version: 2.0.0 KDE Version: 4.4.5 (KDE 4.4.5) QT Version: 4.6.3 Kernel: 2.6.31.13-131 Used versions ----------------------- cdrecord: 3.0 cdrecord ----------------------- scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. Linux sg driver version: 3.5.27 SCSI buffer size: 64512 /usr/bin/cdrecord: Warning: DMA resid 0 for 'read buffer', actual data is too short. /usr/bin/cdrecord: Warning: The DMA speed test has been skipped. Cdrecord-ProDVD-ProBD-Clone 3.00 (i686-pc-linux-gnu) Copyright (C) 1995-2010 Jorg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.9'. Driveropts: 'burnfree' atapi: 1 Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'HL-DT-ST' Identifikation : 'DVDRAM GH22NS50 ' Revision : 'TN02' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: CD-R Profile: DVD-RAM Profile: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD+RW Profile: DVD+R Profile: DVD+R/DL Profile: DVD-ROM Profile: CD-R (current) Profile: CD-RW Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R LAYER_JUMP Drive buf size : 1053696 = 1029 KB Drive pbuf size: 1966080 = 1920 KB FIFO size : 4194304 = 4096 KB Track 01: data 700 MB Total size: 804 MB (79:41.77) = 358633 sectors Lout start: 804 MB (79:43/58) = 358633 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Disk Is not unrestricted Disk Is not erasable Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of lead in: -12508 (97:15/17) ATIP start of lead out: 359845 (79:59/70) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 22 Manufacturer: Ritek Co. Capacity Blklen/Sparesz. Format-type Type 0 2048 0x00 No Media Present or Unknown Capacity Blocks total: 359845 Blocks current: 359845 Blocks remaining: 1212 Starting to write CD/DVD/BD at speed 4 in real SAO mode for single session. Last chance to quit, starting real write in 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Performing OPC... Sending CUE sheet... /usr/bin/cdrecord: WARNING: Drive returns wrong startsec (0) using -150 Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01: 0 of 700 MB written. /usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 01 93 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 2A 00 00 80 30 05 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 200s /usr/bin/cdrecord: A write error occured. /usr/bin/cdrecord: Please properly read the error message above. write track data: error after 825344 bytes Writing time: 78.704s Average write speed 60.8x. Fixating... Fixating time: 0.004s /usr/bin/cdrecord: fifo had 77 puts and 14 gets. /usr/bin/cdrecord: fifo was 0 times empty and 6 times full, min fill was 93%. cdrecord command: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/sr0 speed=4 -sao driveropts=burnfree -data -tsize=358633s - Reproducible: Always OS: Linux (i686) release 2.6.31.13-131 Compiler: i686-pc-linux-gnu-gcc
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!
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!
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!
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!
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!