On Tuesday 04 April 2006 23:44, Mike McCarty wrote: > No, because when K3b calls for the door to close, the automounter > finds it and mounts it. And if it's blank, using this technique > causes the "CD Maker" to start up, preventing K3b from working right. > > The only thing that works on my machine is > > (1) Insert the disc > (2) If it was blank, wait for the CD Maker to start, then kill it > (3) If it was not blank, wait for it to mount, start a CLI, and umount it > (4) Start or continue with K3b. > Much the same can happen in FC4. ISTR that I do have to do the umounting after k3b gets going. There's more than one cause, too, I think. Speaking from memory, there is k3b attempting to automount it. Then there is the removable media attempt to automount it. I just start k3b, then minimise it, wait until everything has had its say, then close or use the umount option, simply making sure that at the end nothing is holding on to it. OK - memory is not the most reliable, but that's the general approach I use. Anne
Attachment:
pgpHU1uX9UwgZ.pgp
Description: PGP signature
