Description of problem: Fails to burn files, images or blank CD/DVD. Version-Release number of selected component (if applicable): gnomebaker-0.6.0-2.fc7 gstreamer-0.10.12-1.fc7 wodim-1.1.6-1.fc7 How reproducible: Always Steps to Reproduce: 1. Run gnomebaker 2. Select clean CD-RW. 3. Actual results: Program asks to insert CD-R. After pressing OK button error message is displayed. Something about wodim. I can't because program hangs. Expected results: Program clean CD-RW. Additional info: In device properties page there are wrong device names /dev/sg0 (writer) and /dev/sg1 (reader). They have to be /dev/scd0 and /dev/scd1. Changing it manually doesn't help- something different happens (I think different error message is displayed), but with the same result. nautilus-cd-burner burns OK. "wodim file.iso" burns OK. wodim -scanbus: scsibus0: 0,0,0 0) * 0,1,0 1) 'HL-DT-ST' 'DVD-RAM GSA-H22N' '1.00' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) * wodim: Warning: controller returns wrong size for CD capabilities page. 1,1,0 101) 'ATAPI-CD' 'ROM-DRIVE-56MAX ' '56JA' Removable CD-ROM 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * wodim -devices wodim: Warning: controller returns wrong size for CD capabilities page. wodim: Overview of accessible drives (2 found) : ------------------------------------------------------------------------- 0 dev='/dev/scd0' rwrw-- : 'HL-DT-ST' 'DVD-RAM GSA-H22N' 1 dev='/dev/scd1' rwrw-- : 'ATAPI-CD' 'ROM-DRIVE-56MAX' ------------------------------------------------------------------------- In stderr message about gstreamer is shown. In stderr message about ioctl fail is shown.
Created attachment 158305 [details] stderr
I have the same problem width HL-DT-ST DVDRAM GSA-4163B
wodim without parameters burns OK.
I also failed to make gnomebaker burn. I tried to make an audio CD. Gnomebaker converted wavs to cd audio and then started to burn, but hung indefinitely, consuming the cpu. I got no error message from it. cdrecord -scanbus says scsibus0: 0,0,0 0) 'TSSTcorp' 'CD/DVDW SH-S183L' 'SB01' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * Using wodim from the command line worked just fine, on the same disk. Apparently gnomebaker never did anything to the blank disk, because the disk worked with no problems afterwards. So the kernel and wodim seem to be fine, but gnomebaker does not seem to detect a blank disk corrently. Relevant versions: gnomebaker-0.6.0-2.fc7 wodim-1.1.6-1.fc7 kernel-PAE-2.6.22.1-41.fc7
I have had the exact same problem ever since Fedora 7 was released. The incorrect device name is being auto-detected and if I try to burn it hangs indefinitely. As a workaround I've had to use GnomeBaker for generating an ISO, and then take the ISO and go to the command line and use "wodim filename.iso" to burn it.
The new gnomebaker-0.6.1 should be in the updates soon. Please try to update and let me know if the new version works.
I updated to 0.6.1 and it still hangs indefinitely. CD device is still being auto-detected as /dev/sr0.
I have the same problem with GnomeBaker 0.6.1-2.fc7. Wodim works fine from terminal, but wodime give me an error and hungs. I run it as normal user, but if I run it as root give the same error too. This is the error message: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. scsidev: '1,1,0' scsibus: 1 target: 1 lun: 0 WARNING: the deprecated pseudo SCSI syntax found as device specification. Support for that may cease in the future versions of wodim. For now, the device will be mapped to a block device file where possible. Run "wodim --devices" for details. And this is the output from the console: [francesco@Fedora ~]$ gnomebaker (process:5682): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. ** (gnomebaker:5682): WARNING **: devices_is_disk_inserted - ioctl failed ** (gnomebaker:5682): WARNING **: devices_eject_disk - Error opening device è\ u0008/sr0
(In reply to comment #8) > Wodim works fine from terminal, but wodime give me an error and hungs. Edit: => Wodim works fine from terminal, but GnomeBaker give me an error and hungs.
The problem seems to be that wodim since 1.1.5 doesn't like the old dev=b,t,l syntax. I have undertaken another attempt (0.6.1-3) to fix the problem. Unfortunately I could test the latest patch only briefly -- I do not have a suitable F-7 box with burner yet.
Tomas, if you want to pass tests by me before sending them to updates I am up for it. I have separate 32-bit and 64-bit F7 systems. Feel free to drop an e-mail.
Thank you Michael, but that won't be necessary. I already have a testing hardware. It was really cdrecord/wodim incompatibilty that caused the problems. The new release 0.6.1-4 was pushed to the testing repository and it seems to be working OK.
OK, 0.6.1-3 rolled into updates and I updated my systems. It still autodetects my device node as /dev/sr0, which is still incorrect. I am not able to burn an ISO until I change it to /dev/scd0. Burning and/or copying a CD/DVD results in the same lookup as before. Some warning text is output: "WARNING: the deprecated pseudo SCSI syntax found as device specification. Support for that may cease in the future versions of wodim. For now, the device will be mapped to a block device file where possible. Run "wodim --devices" for details." Shortly after there is some more text that I cannot read and it locks up and I have to kill gnomebaker.
Thanks for testing, but 0.6.1-3 is definitely not OK. I really meant 0.6.1-4 which is in the testing repository (e.g., ftp://ftp.fi.muni.cz/pub/linux/fedora/linux/updates/testing/7/i386/gnomebaker-0.6.1-4.fc7.i386.rpm) On my system /dev/scd0 is just a symling to /dev/sr0.
On my two test systems (one 32-bit, P4 based, one 64-bit, Core 2 based) the device node /dev/sr0 does *NOT* exist. The device node /dev/scd0 is the hard character device and *NOT* a symlink. I updated to 0.6.1-4 and it fails to burn because the device node is incorrect. If I manually override it to /dev/scd0 then it will burn. I have not modified my udev files.
I have no reason to lie... [tsmetana@vmware187 ~]$ ll /dev/scd0 lrwxrwxrwx 1 root root 3 2007-09-06 07:25 /dev/scd0 -> sr0 If you could "cat /proc/sys/dev/cdrom/info" -- GnomeBaker takes the information from that file (which may be wrong).
My /proc/sys/dev/cdrom/info states sr0, but my device node is scd0... what's going on? The 0.6.2-1 update broke burning again. It "calculates image size" for a few seconds and then spits out "Failed" and doesn't burn anything. There is no output in the little detail box. I'll have to roll back to 0.6.1-4 for now.
Sorry for that Michael (and everyone). There is a regression in the upstream GnomeBaker and I didn't find it (tested with cdrtools backend) -- should be fixed in 0.6.2-2.
For those having problems with wrong device detection, please refer to the bug #307051.
(In reply to comment #19) > For those having problems with wrong device detection, please refer to the bug > #307051. Cool, thanks! I'm ready to close this bug if everyone else is.
Haven't heard any complaints for some time I consider this problem being resolved.