Bugzilla – Bug 105590
K3B cannot burn a CD with individual boot image added
Last modified: 2006-02-06 12:59:38 UTC
After setting up what to burn and finally like to write I get a popup that complains that I should insert a writeable/appendable disk. Seems as if k3b thinks I have a normal CD in the drive? The problem probably lays deeper? IIRC there wasn't anything in /var/log/messages. Tell me what logs or whatever I can provide. The burner worked fine with SL 9.3 Ah yes, another minor bug seems to be: I only marked: Create ISO image, but k3b still seems to touch the hardware and complains as described above -> image is deleted. Just wanted to mention that...
it works fine on my beta2/i386 laptop
to rule out permission problems: update or fresh install? Is your recorder listed in lshal and does it have a resmgr.class property? Is an acl set on the recorder device (use getfacl to check)?
fresh install. resmgr.class='cdrom' storage.cdrom.write_speed = 2822 storage.cdrom.cdrw = true storage.cdrom.cdr = true ... Strange, from these hal variables it seems as if it's not DVD write capable, but I think it is -> at least it's written on the cover... However, it would be nice enough if I could even write a CD. I am not very familar with cdrecord and the lower CD writing stuff. Maybe then this one could be reassigned to some HW guy, I doubt that it's k3b fault? Any help how to debug this further is appreciated.
hwinfo --cdrom ?
Sorry, as said, I haven't used much cdrecord/mkisofs tools. cdrecord works as root and as normal X-user (trenn). So it has nothing to do with user rights, but may really be a k3b bug?
I have a similar problem with an external (DVD) burner. Wehn I try to burn a DVD project then it tells me to insert a Double Layer DVD and when I try to burn a CD project then it tells me to insert a CD (CD is inserted). The problem here is definitely a permission problem. brw-r----- 1 root disk 11, 0 Aug 26 13:22 /dev/sr0
Created attachment 47764 [details] hwinfo --cdrom
sorry, but is this still the case? And do you have x86_64 too?
Marco's seem to be unrelated, for me it's not the access rights. Those seem to be only messed for external drives (/dev/srX or whatever)? Did you want to set the needinfo to mmichna? I reported the bug and already set the hardware to x86_64.
OK, CD-burning seems to work in general (tested on Beta4plus). I created a CD-image and called: k3b --image PATH k3b then seems to go throw the windows as if clicked by mouse and checks the image. Clicking Start in the popped up Dialog works. What I tried before was: 1) Creating an empty CD project 2) Project->Edit Boot Images->new 3) Adding a FreeDos boot image, it gets checked and is accepted 4) Open the burn dial, start burning and immediately this window pops up: Found media: CD-R (empty) Please insert a complete or appendable CD-R(W) medium into drive TOSHIBA ODD-DVD SD-R6252 (/dev/hdc) *Load* *Eject* *Force* *Cancel* I am pretty sure I could burn bootable CDs like that on 9.3. Did I miss something, or is k3b messing something up creating a boot iso and the message is just totally wrong? This one is probably totally unrelated to Marco's device access problem. Feel free to lower severity or set it on INVALID if I did something wrong or LATER (as this won't be fixed for 10.0?)
ok, now I fail to see where the bug is.. you don't want the popup? you already entered a blank cd?`
I have a 1.44MB freedos boot image. How can I burn a bootable CD with k3b. I could do it with 9.3 k3b (see steps described in #10 - I think I've done it that way).
thanks to assigning the bug to us! :-) anyway, i just tried to create a bootable image with 10.0 k3b, works for me. No, i don't tried to burn it. It complained that no burner was build in (wrong) and let me made the image. I will close this bug now. Try with 10.1, if the problem is still there, please reopen.