[Bug 14394] cdrecord/k3b/nautilus problem
Richard Kleeman
kleeman at cims.nyu.edu
Sun Jan 29 17:46:39 UTC 2006
Public bug report changed:
https://launchpad.net/malone/bugs/14394
Comment:
OK I think I may have made some progress on this.
As noted above If I insert the cdrw into the drive in gnome (or kde or
xfce) it produces all the kernel error messages noted above. If I run
from a 'init 1' terminal no error messages are produced.
Now in gnome if I issue
cdrecord -balnk=fast
cdrecord -dao -v -data dsl-2.1b.iso
everything WORKS FINE (as it does in the 'init 1') except that the
following message is prduced by cdrecord in gnome but not the terminal:
Error trying to open /dev/cdrw exclusively (Device or resource busy)...
retrying in 1 second
During the burn no kernel error messages are produced but as soon as the
burn finishes (successfully) the kernel error messages resume and I can
see the green lights flickering (this happens when a burnt cd-rw is
inserted in anycase)
This all suggests to me strongly that it is gnome (or kde) trying
(unsuccessfully) to mount or recognize in some fashion the media that is
the source of the problem.
Mounting from an 'init 1' terminal works just fine by the way.
Finally the sg module being present makes no difference to the above. I
rmmoded it and nothing changed.
I also rmmoded sr_mod and the kernel errors did not occur but then
cdrecord could not find the drive.
More information about the kernel-bugs
mailing list