pccasto / rubyripper

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

GUI does not display progress information, instead reverting to track selection #227

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Rip CD

What is the expected output? What do you see instead?
First track starts to rip and GUI reverts from updating to the tracklist
selection.

What version of rubyripper are you using? On what operating system? Are you
using the gtk2 or the commandline interface?
svn 305, gtk2

Please provide any additional information below.
./rubyripper_gtk2.rb: line 265
   Gtk-CRITICAL **:gtk_text_layout_get_iter_location: assertion
`GTK_IS_TEXT_LAYOUT (layout)' failed
./rubyripper_gtk2.rb: line 265
   Gtk-CRITICAL **:gtk_text_layout_get_iter_location: assertion
`GTK_IS_TEXT_LAYOUT (layout)' failed
./rubyripper_gtk2.rb: line 265
   Gtk-CRITICAL **:gtk_text_layout_get_iter_location: assertion
`GTK_IS_TEXT_LAYOUT (layout)' failed
Adding track 1 (wav) into the waitingroom..
Inside handleThreads: maxthreads = 0, threads = 0
busytracks = 1, track = 1, codec = wav

Original issue reported on code.google.com by mordbr...@gmail.com on 17 Aug 2008 at 2:32

GoogleCodeExporter commented 8 years ago
I trust this also happens when extra encoding threads are disabled?

Original comment by rubyripp...@gmail.com on 18 Aug 2008 at 6:27

GoogleCodeExporter commented 8 years ago
Yes, extra encoding threads set to 0 and it still happens.

Original comment by mordbr...@gmail.com on 19 Aug 2008 at 4:40

GoogleCodeExporter commented 8 years ago
Seems to be fixed with svn 307?  Weird.

Original comment by mordbr...@gmail.com on 22 Aug 2008 at 2:11

GoogleCodeExporter commented 8 years ago
If you say so....

Original comment by rubyripp...@gmail.com on 22 Aug 2008 at 3:51

GoogleCodeExporter commented 8 years ago
I wish I could remember which disc(s) the problem happened with so I could test
again... but the last 4 discs I've ripped have been fine so i can't reproduce 
it.

Original comment by mordbr...@gmail.com on 22 Aug 2008 at 7:54

GoogleCodeExporter commented 8 years ago
Well if the problem occurs again, make sure to revive this one ;) And you never 
know,
commit 307 might actually have fixed your problem.

Original comment by rubyripp...@gmail.com on 22 Aug 2008 at 8:06

GoogleCodeExporter commented 8 years ago
Of course!  You are right, the last commit could have fixed it... I've seen
whitespace mess up code before, so you never know.

Original comment by mordbr...@gmail.com on 22 Aug 2008 at 8:36