Hi Tony, "cdparanoia -v -Q" worked just fine. Then I realized I couldn't check the ripperx configuration directly for the ordinary user because the app wouldn't even start.... then I looked at .ripperXrc directly and didn't know what I was looking at.... then it occurred to me, "hey, maybe there is a problem with this rc file".....
Sure enough, I moved the old .ripperXrc out of the way, and ripperx started up just fine, and completed a test rip. FYI: $ diff .ripperXrc.old.broken .ripperXrc.new.works 8c11 < //-V 2.6.1 --- > //-V 2.7.0 10,11c13,14 < General::WavRatio = 0.011166 < General::Mp3Ratio = 0.008863 --- > General::WavRatio = 0.006000 > General::Mp3Ratio = 0.080000 23c26 < Ripper::Ripper = cdparanoia -s -d /dev/scd0 -v --- > Ripper::Ripper = cdparanoia 28a32 > Encoder::Priority = 10 32c36 < Encoder::fullCommand = lame -b 128 --nohist -v -h -V 4 --- > Encoder::fullCommand = lame -b 128 45a50 > CDDBConfig::CreatePlaylist = 1 I am guessing "-d /dev/scd0 -v" was the problem? I vaguely recall that my disk was pretending to be a SCSI for a few kernels. Sorry to bother you for something I should have figured out myself. One thing to note, though, if that blank error box had told me what device it was trying to access, instead of being unhelpfully and completely blank, I probably would have figured this out myself. Thanks for the pointers, and go ahead and close this bug, unless of course you want to use it to fix that error popup. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
