rlishtaba / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

GUI fails silently when lame is selected and the lame package is not installed #410

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install rubyripper on a system without lame installed
2. Select "Lame MP3" as the encoding method
2. Insert a CD and click the "Rip CD Now!" button.

What is the expected output? What do you see instead?
Expected output: an error message indicating that lame is not installed,
debugging information on the console (assuming debugging is enabled)
Actual output: Clicking the "Rip CD" button has no effect. Nothing
whatsoever is logged on the console

1) What version of rubyripper are you using? On what operating system?
-> 0.5.7 from the Ubuntu repositories on Jaunty Jackalope (9.10)

2) Are you using the gtk2 or the commandline interface?
-> gtk2

3) Is the problem gone with the default settings? If so, please attach your
settings file ($HOME/.rubyripper/settings).
-> No

4) Does the problem only happen on a specific disc? If so, please attach
the output of cdparanoia -Q. Also the freedb output would be nice if it may
be related to it.
-> No

Please provide any additional information below.

Original issue reported on code.google.com by rgste...@gmail.com on 8 Mar 2010 at 2:05

GoogleCodeExporter commented 8 years ago
I can confirm this bug. I had the same issue, so I came here, read that, 
installed
lame and all works fine now. BTW: I did not had enabled mp3 encoding - only 
Vorbis.

Original comment by thomas.h...@gmail.com on 9 Apr 2010 at 7:39

GoogleCodeExporter commented 8 years ago
I cannot reproduce this problem with latest git.

After removal of lame I get the following behaviour:
1) when selected flac there are no problems and ripping starts
2) when selected vorbis there are no problems and ripping starts
3) when selected mp3 an error message is displayed that the lame binary is 
missing. 
The ripping is cancelled and the user is shown the disc info after a few 
seconds.

Therefore I suppose it is fixed meanwhile.

Original comment by boukewou...@gmail.com on 24 Apr 2010 at 10:33