Bugzilla – Bug 149233
Problems burning cd's with k3b
Last modified: 2008-06-25 09:53:35 UTC
Using k3b all reading functions are functional until the burning process is to start. Then k3b hangs up (no possibility of closing k3b, even after abort burning cd). The only remedy is to restart at least the x-server. Bug description delivered by bug-report program of k3b: K3b Version: 0.12 KDE Version: 3.4.2 Level "b" QT Version: 3.3.4 Kernel: 2.6.13-15-default Devices ----------------------- JLMS XJ-HD166S DIS3 (/dev/hdc, ) at /media/dvd [CD-Rom; DVD-Rom] [DVD-Rom; CD-Rom] [Keine] CyberDrv CW088D CD-R/RW 110F (/dev/hdd, ) at /media/cdrecorder [CD-R; CD-RW; CD-Rom] [CD-Rom; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R] Used versions ----------------------- cdrecord: 2.1 cdrecord ----------------------- scsidev: '/dev/hdd' devname: '/dev/hdd' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. Linux sg driver version: 3.5.27 /usr/bin/cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). SCSI buffer size: 64512 /usr/bin/cdrecord: Success. read buffer: scsi sendcmd: no error CDB: 3C 00 00 00 00 00 00 FC 00 00 status: 0x4 (CONDITION MET/GOOD) resid: 64512 cmd finished after 30.247s timeout 200s Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM Using libscg version 'schily-0.8'. Driveropts: 'burnfree' atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'CyberDrv' Identifikation : 'CW088D CD-R/RW ' Revision : '110F' Device seems to be: Generic mmc CD-RW. Current: 0x0009 Profile: 0x000A Profile: 0x0009 (current) Profile: 0x0008 Profile: 0x0002 Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1806336 = 1764 KB FIFO size : 4194304 = 4096 KB cdrecord command: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdd speed=48 -dao driveropts=burnfree -eject -data /tmp/kde-root/k3b_0.iso I don't know why derecord identifies my cd-burner as a scasi-drive while any scasi controller is installed on the computer.Using other programs all cd devices are usable. Please send some help, because I didn't found functional hints in several groups. Thanks a lot!
Hello Andreas, cdrecord works with SCSI-drives only and an emulation interface is used for IDE drives, so this is perfectly normal. As yto your problem: Have you tried running cdrecord from the shell? Please do this first and attach any output shown here, this problem might be located there or within the hardware. If it does work in the shell, it's likely a k3b problem.
Please reopen this report if you can provide the required information.
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(