Closed GoogleCodeExporter closed 8 years ago
Also happens with a copy from Git taken today, 5 July 2010.
Original comment by cowbu...@gmail.com
on 5 Jul 2010 at 6:02
Same here. 0.6.0 from from the download or from git. CLI works fine,
graphical interface hangs.
Original comment by andrew.h...@gmail.com
on 5 Jul 2010 at 6:05
What is your version of ruby and ruby-gtk?
Original comment by boukewou...@gmail.com
on 5 Jul 2010 at 6:08
ruby version=1.8.7_p249
ruby-gtk2 version=0.19.1
on gentoo
Original comment by andrew.h...@gmail.com
on 5 Jul 2010 at 6:23
Is there any error related info visible when launched from a terminal?
Original comment by boukewou...@gmail.com
on 18 Jul 2010 at 9:25
You might wanna set the value of create_cue to false and see if it helps. See
the settings file $HOME/.config/rubyripper/settings.
Otherwise uprading to ruby-1.9 will probably solve your problems.
Original comment by boukewou...@gmail.com
on 24 Jul 2010 at 10:35
Hello, I am a long time user of ruby ripper and it worked always great for me.
This weekend I upgraded from opensuse 11.2 to 11.3 and now rubyripper fails
with exactly the same error as described above.
I digged a little in the code and what fails is the initial call to
scan_drive(). In scan_drive it is the Disc.new command which fails. As a test I
commented out the Thread.new (and the corresponding end). Now things work
better. I have not yet checked if everything works. But I guess there is a
problem with the multithreading. If you want me to provide more info, please
tell me what.
Cheers
Frank
Original comment by frank.st...@web.de
on 16 Aug 2010 at 7:22
#5 - do you mean if you do cdparanoia it does keep spinning or it just displays
the toc like normal and spins down? I'm unclear about that.
Original comment by mordbr...@gmail.com
on 27 Sep 2010 at 1:52
I can confirm that the hack mentioned in #7 works for me on Fedora 12.
Original comment by rghec...@gmail.com
on 5 Oct 2010 at 9:02
This is in no way reproducable. I guess the right way to solve this is to file
a bug at your distribution to upgrade to a Ruby 1.9 version. It's out there for
almost four years, so one can hardly call it bleeding edge, right?
Original comment by boukewou...@gmail.com
on 13 Nov 2011 at 10:42
Original issue reported on code.google.com by
tonyrie...@gmail.com
on 1 Jul 2010 at 8:11