Version: 0.11.23 (using KDE 3.4.0, compiled sources) Compiler: gcc version 3.3.4 OS: Linux (i686) release 2.6.11.7 When I attempt to burn CDs using k3b 0.11.23, whether from files dragged to the area or by burning an iso image, k3b returns error 255. This can be reproduced on my box as follows: 1) Click on Tools -> CD -> Burn CD Image... 2) Select the ISO image to be burned to CD. 3) After the md5 sum is verified, click the Start button. 4) Error messages appear as follows: * cdrecord returned an unknown error (code 255) * Unknown error 255 * Please send me an email with the last output Below is the output from the most recent instance of this error: Devices ----------------------- HP CD-Writer+ 8200 1.0f (/dev/sr0, ) at [CD-R; CD-RW; CD-ROM] [Error] [SAO; TAO; RAW; RAW/R96R] LITEON CD-ROM LTN382 UL2B (/dev/hdc, ) at /mnt/cdrom [CD-ROM] [Error] [None] System ----------------------- K3b Version: 0.11.23 KDE Version: 3.4.0 QT Version: 3.3.4 Kernel: 2.6.11.7 cdrecord ----------------------- /usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 /usr/bin/cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI driver. /usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. /usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=2,0,0 speed=4 -eject -data /mnt/dos/g4l-v0.16.iso
Did you try re-running the Setup program?
Dik, I have re-run the setup program. All the permissions have been set correctly, at least as far as k3b is concerned. I also informed the "meister" of the distro I use about the issue. He believes it may have to do with the file system on the host machine on which the distro ISO was built (reiserfs) vs. the file system I used at the time I installed the distro (ext3). I was able to burn cd's with xcdroast on that particular box, but I'd much rather use k3b, as it's so far superior a front-end than xcdroast. Thanks for your question. John On 20 Jun 2005 12:48:10 -0000, Dik Takken <d.h.j.takken@phys.uu.nl> wrote: [bugs.kde.org quoted mail] Dik,<br> <br> I have re-run the setup program. All the permissions have been set correctly, at least as far as k3b is concerned.<br> <br> I also informed the "meister" of the distro I use about the issue. He believes it may have to do with the file system on the host machine on which the distro ISO was built (reiserfs) vs. the file system I used at the time I installed the distro (ext3). I was able to burn cd's with xcdroast on that particular box, but I'd much rather use k3b, as it's so far superior a front-end than xcdroast.<br> <br> Thanks for your question.<br> <br> John<br><br><div><span class="gmail_quote">On 20 Jun 2005 12:48:10 -0000, <b class="gmail_sendername">Dik Takken</b> <<a href="mailto:d.h.j.takken@phys.uu.nl">d.h.j.takken@phys.uu.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=107703">http://bugs.kde.org/show_bug.cgi?id=107703</a><br><br> <br><br><br>------- Additional Comments From d.h.j.takken phys uu nl 2005-06-20 14:48 -------<br>Did you try re-running the Setup program?<br></blockquote></div><br>
make sure the sg driver is loaded and you have write permission to the sg devices.
Sebastian, As it turned out, the /dev directory didn't have any sg nodes in it at all. Once I executed the command modprobe sg, the node was there. I was able to burn CD's. I've also brought this issue to the distribution's maintainer for his action. Best, JOhn On 21 Jun 2005 13:09:09 -0000, Sebastian Trueg < trueg@informatik.uni-freiburg.de> wrote: [bugs.kde.org quoted mail] Sebastian,<br> <br> As it turned out, the /dev directory didn't have any sg nodes in it at all. Once I executed the command modprobe sg, the node was there. I was able to burn CD's.<br> <br> I've also brought this issue to the distribution's maintainer for his action.<br> <br> Best,<br> JOhn<br><br><div><span class="gmail_quote">On 21 Jun 2005 13:09:09 -0000, <b class="gmail_sendername">Sebastian Trueg</b> <<a href="mailto:trueg@informatik.uni-freiburg.de">trueg@informatik.uni-freiburg.de</a>> wrote: </span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter. <br><br><a href="http://bugs.kde.org/show_bug.cgi?id=107703">http://bugs.kde.org/show_bug.cgi?id=107703</a><br><br><br><br><br>------- Additional Comments From trueg informatik uni-freiburg de 2005-06-21 15:09 -------<br> make sure the sg driver is loaded and you have write permission to the sg devices.<br></blockquote></div><br>
Based on my e-mail reply to Sebastian (running modprobe sg created the necessary nodes for CD burning), this "bug" is resolved.