Can't burn CDs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cdrtools (Ubuntu) |
Invalid
|
Medium
|
Scott James Remnant (Canonical) |
Bug Description
I tried to burn a CD-R today and discovered that it didn't work anymore. I tend
to think that it's due to udev but it could also be a bug in cdrecord.
If I try to burn using nautilus-cd-burn, rhythmbox or serpentine, I always get
the same behaviour: the CD writer is detected correctly, the image is created,
and finally the burning fails but no data is written on the CD. Thus, the CD can
be re-used.
If I try to burn using graveman, the CD writer is detected too, but when I
launch the actual burning, it refuses to go on, saying that there is no CD in
the writer.
Finally, I tried to perform a cdrecord -scanbus, and here is what I got:
root@lifebook ~ # cdrecord -scanbus
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to
<email address hidden>.
The original author should not be bothered with problems of this version.
cdrecord: Warning: Running on Linux-2.6.15-7-386
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI
driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord:
cdrecord: For more information, install the cdrtools-doc
cdrecord: package and read /usr/share/
Any idea ?
PS: it used to work last time I tried, on the same PC (a few months ago). I also
tried on a Windows PC with the same CDs, and it worked.
Definitely not a udev bug, if udev is loading the right driver and the device
node is being created, then its job is done. It has no further involvement than
that. Unless you know that the device node is wrong (for example, are the
permissions correct?) then I don't see how this is a udev bug.