Bug 350918 - whenever i try to burn sth. cdrecord crashes
Summary: whenever i try to burn sth. cdrecord crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Data Project (show other bugs)
Version: unspecified
Platform: Other FreeBSD
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-03 14:28 UTC by vavatch2309
Modified: 2022-11-23 05:16 UTC (History)
3 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 vavatch2309 2015-08-03 14:28:22 UTC
Devices
-----------------------
ASUS DRW-20B1LT 1.01 (/dev/cd0, 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]

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.14.3
QT Version:  4.8.6
Kernel:      10.1-RELEASE-p16

Used versions
-----------------------
cdrecord: 3.1a24

cdrecord
-----------------------
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
SCSI buffer size: 65536
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
Cdrecord-ProDVD-ProBD-Clone 3.01a24 (amd64-unknown-freebsd10.1) Copyright (C) 1995-2014 Joerg Schilling
TOC Type: 3 = CD-ROM XA mode 2
Waiting for data on stdin...
Using libscg version 'schily-0.9'.
Driveropts: 'burnfree'
atapi: 0
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'ASUS    '
Identifikation : 'DRW-20B1LT      '
Revision       : '1.01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: DVD-RW sequential recording
Profile: DVD+R/DL 
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-R/DL layer jump recording 
Profile: DVD-R/DL sequential recording 
Profile: DVD-RW sequential recording (current)
Profile: DVD-RW restricted overwrite (current)
Profile: DVD-RAM 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Profile: Removable Disk 
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED 
Supported modes: PACKET SAO LAYER_JUMP
Drive buf size : 1310720 = 1280 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data  2270 MB        
Total size:     2270 MB = 1162521 sectors
Current Secsize: 2048
Blocks total: 2297888 Blocks current: 2297888 Blocks remaining: 1135367
Forcespeed is OFF.
Starting to write CD/DVD/BD at speed 4 in real SAO mode for multi 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.
Starting new track at sector: 0
Track 01:    0 of 2270 MB written.
cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 00 00 00 00 00 20 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 64 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0
Sense flags: Blk 0 (not valid) 
resid: 65536
cmd finished after 0.272s timeout 200s
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
write track data: error after 0 bytes
Writing  time:    6.905s (00:00:06.905)
Average write speed 295.7x.
Fixating...
cdrecord: Input/output error. close track/session: scsi sendcmd: retryable error
CDB:  5B 01 02 00 00 01 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 72 04 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x72 Qual 0x04 (empty or partially written reserved track) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.078s timeout 480s
Fixating time:    0.151s (00:00:00.151)
cdrecord: fifo had 64 puts and 1 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
BURN-Free was not used.

cdrecord command:
-----------------------
/usr/local/bin/cdrecord -v gracetime=2 dev=1,0,0 speed=4 -sao driveropts=burnfree -multi -waiti -xa -tsize=1162521s -


Reproducible: Always

Steps to Reproduce:
1.I commence a compilation by adding files.
2.I hit the burn button
3.The log windows shows I/O errors are occuring, then cdrecord reports crash

Actual Results:  
K3B tells me to file an error report, cdrecord returned an unknown error code 254.

Expected Results:  
It should have burned.

I am running GhostBSD 10.1 with the latest patches.
Comment 1 Leslie Zhai 2016-09-06 09:23:55 UTC
Hi vavatch2309, Did you use this cdrecord http://cdrtools.sourceforge.net/private/cdrecord.html
please do not use cdrkit!
Comment 2 Justin Zobel 2022-10-24 00:46:28 UTC
Thank you for reporting this bug 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 3 Bug Janitor Service 2022-11-08 05:09:58 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 4 Bug Janitor Service 2022-11-23 05:16:26 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!