OK...now this is getting interesting...

First of all, yes this does happen with all discs I've put in there...unfortunately...

Second of all, I'm not sure what you have in mind with the solution involving Wine, but I'm pretty sure it's not going to be a solution for me. I've yet to install Wine, and it just seems kind of wrong to me to do so...I guess keep me posted though...

Now, I've figured out a couple of things...first of all, I remember Ubuntu having weird permission issues every now and then back when I was running it, so I decided to run Grip as root. Seemed to go a lot faster...it's actually ripping as I type, though it seems to have the same problems with that last 1.5% of a track.

When I started grip in xterm, I did have one error message, but it looks benign:
You be the judge on that. As for the tail -f /var/log/messages, I've got to say that's one of the more useful tricks I've learned in a while. And yes, it's pumping out one heck of a lot of stuff when I run this. I put the stuff that came up today online for ya'all, cause it's long. Click here for a copy of /var/log/messages

This make any sense to anybody?

Thanks again for all the help. Progress can be tough...

Ok....first of all, acting with wine sucks! It is slowing down everything, and removes, sometimes, the bootloader. So I removed wine... Now, about cd-ripping: every ripping program is working like: read track->analize->merge tag->encode->write to location(save). If the ripping program hungs in one of second to final step, there is a possible driver that is a bit conflicting with some others. The "analize" and "encode" section use in allmost cases the sound card. In my case, i found the same error messages when I was use via sound library...and I have ALC850 instead... after upgrading the kernel, drivers, and programs, Grip started with 1'st cd to work well, and never generated errors;) It was a moment of triumf for me, but now I think I just was lucky. If I'm wrong, please tell me!

If its working its working I think...as long as there are no errors any more it might just habe been an issue with the sound kernel module.

What also makes a big difference during rippinga nd encoding is the encoder that u use. I use LAME and it has been very good for me. I find it seems to work the fastest and with very good results.

Happy its working now.

Cheers

Yeah, I pretty much give up. I don't know how to upgrade the kernel, and besides, I have a fairly recent version...hardware support - Linux's achilies heel.

If anybody reading this someday has a theory for me, let me know. Until then, I'm going to...

...be using my other computer with an OS that understands its hardware...Ubuntu.

I'm trying to use Sound Juicer or Grip, but both do the same thing to me. I install all the libraries mentioned above and everytime I try to rip a cd it comes up as an .ogg file in the directory where it's ripped to. I don't understand why it does that even after I read through the manuals and put in the string to let it know how to rip as .mp3

Reading through this I'm either to tired or dumb to fully comprehend it all. So could anyone through it into a nutshell quickly on how to get anything to rip as .mp3 format without takeing 30min per cd?

Yes lame and other libs are installed.

Thanks.

mlissner, have you got SELinux enabled?
If you have try disabling it.

Click -> System -> Administration -> Security level and Firewall.
Select the SELinux Tab -> Change SELinux Setting to Disabled.

Reboot.

- or -
on the command line
should show you if its enabled or not. (permissive or enabled)

Cheers

I do have selinux enabled, but I'm not sure that I want to disable it. I did some reading up on it, and it seems like a good thing for my computer (despite the fact that it slows it down). I'm planning on soon making this computer a server, so when that day comes, I'm going to want selinux.

You really think that's it?

Neo_granas - if you contact me via AIM or personal email, we can try to sort this out one on one and post back. I'm not sure of your setup without you providing more details.

I'm not sure but the errors in your dmessage suggest a security problem.

Just give it a try. You can turn it back on again if it does not help.

I find that SELinux interfears with a lot of services...

Cheers