Anyone experienced this with k3b?
 

I installed k3b from source on Slack 10 , 2.4.26 and everytime I burn a CD it goes to 50% on the overall progress, but in the box above it says writing completed successfuly. Then pops up a message saying reload medium and ejects the cdrom and then after I close the tray back it says unable to read iso 9660 filesystem. I believe that last thing is because it is searching for an empty CD, but I wonder why it would do that since it writes everything fine. I check my cds after burning and they are fine, and k3b says written 689 of 689 Mbs for example.


I also have another problem my umount and eject unmount the cd-r's , but do not eject them and I cannot eject them manually either.

Any suggestions? Any help will be greatly appreciated

This is probably not a function of k3b, but of the underlying cd record programs. K3b has an option to generate a debug log. Can you do so and post the output here?

(Disclaimer: I've only used K3B a few times... the following opinion is just guesswork.)

I think the default for K3B is to verify the disk by reading it after writing... I remember being surprised that it ejected the disk after the write but before doing the verification step.

So... I think the 50% progress is saying that half of the overall progress (all of the writing, none of the reading) has finished. It's not clear (at least to me) in your post if you're leaving the burned CD in the drive when you close the tray... K3B is expecting you to leave the CD in the tray and close it so that it can read it and verify that everything worked.

If you're already keeping the CD in the tray, then something more sinister is going on... see if you can find that debug log that was mentioned previously.

As far as your other problem, I don't have any ideas...

Thank you rhatchThat's exactly what the problem was. It was new to me because I didn't have that problem with my previous distributions. I also apologize for not replying sooner. I had a very busy week at school. This just makes me love Linux even more. This is the only operating system where you can fix and tweak pretty much everything and when you have a problem with something, it is because you are not doing something right, not because someone somewhere didn't do his job right. BTW how is Gentoo and Debian compared to Slackware. I really love slack, but I am also thinking about trying Gentoo and Debian just to check them out.
Thanks for everyones replies.

:D :) :)

Glad I could help... I've never liked writing, and it's nice to know that it was worth the effort.

As far as distros, you really should try them yourself and see what you think. I've never really tried Slackware long-term, so I can't compare.

When/if you try Debian, I recommend using the testing release (3.1? a.k.a. Sarge) not the stable release (3.0 a.k.a. Woody)... I found the installer MUCH easier to use and the packages are much more current. I've had problems getting the X windows installer to auto-detect video settings properly in some cases... improvements may have been made by the time you try, but in any case it seemed to work more consistently for me if I picked the "Desktop" group (IIRC) when the install asks about additional package groups.

I've tried Gentoo and recommend it at least as a learning experience (the install documentation is excellent). I used it for a few months before I got tired of compiling everything myself... you may find you like it. In theory, Gentoo also supports binary packages... but I never tried to use that option.

If you try Gentoo and decide you want more control or a more in-depth learning experience, check out Linux from Scratch (www.linuxfromscratch.org).