Hello Michelle, Can you test with cdparanoia alone? ripperx doesn't doesn't invoke modprobe (obviously it does invoke cdparanoia), and sounds more like a problem with how cdparanoia is interacting with the kernel on your system. It might be helpful to see the contents of dmesg after this occurs.
Thanks, tony mancill Michelle Konzack wrote: > Package: ripperx > Version: 2.6.4-2 > Severity: normal > > Error description: > > Today I have installed "ripperx" and after configuring, I have tried to > scan a CD but it hangs at cdparanoia/modprobe. After waiting some time > (~15 minutes) the ripperx window was not more updated (I can erase > contents with other windows) and I had 6 open Error boxes without any > contents... > > ^C does not work, even if ripperx was started from an xterm to see > possible error messages. only a 'kill -9 PID' had helped and then I > have had to kill the pids of cdparanoia and modeprobe. > > After arround 1/2 hour the riperx window comes back and show me an Error > Code 14 (can not open CD-Drive) which is not possibel, because all other > tools (cdda, cdtools, xmms, vlc, xine, ...) can access the drive which > is definitivly /dev/scd0 (DVD/CD). > > If you need more informations, please let me know. > > Greetings > Michelle Konzack > > > > -- System Information > Debian Release: 3.1 > Kernel Version: Linux michelle1.private 2.4.27-2-386 #1 Wed Aug 17 09:33:35 > UTC 2005 i686 GNU/Linux > > > Versions of the packages ripperx depends on: > ii cdparanoia 3a9.8-11 An audio extraction tool for sampling CDs. > ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries and Timezone
signature.asc
Description: OpenPGP digital signature
