| 2010-01-30 21:52:55 |
Aiden Nibali |
bug |
|
|
added bug |
| 2010-02-19 02:16:13 |
Mike Massonnet |
attachment added |
|
ruby-gnome2-gtk-thread-patch.debdiff http://launchpadlibrarian.net/39385299/ruby-gnome2-gtk-thread-patch.debdiff |
|
| 2010-02-19 02:30:16 |
Brian Murray |
tags |
|
patch |
|
| 2010-02-19 21:30:31 |
Brian Murray |
nominated for series |
|
Ubuntu Karmic |
|
| 2010-02-19 21:30:31 |
Brian Murray |
bug task added |
|
ruby-gnome2 (Ubuntu Karmic) |
|
| 2010-02-19 21:32:02 |
Brian Murray |
ruby-gnome2 (Ubuntu): importance |
Undecided |
Medium |
|
| 2010-02-19 21:32:02 |
Brian Murray |
ruby-gnome2 (Ubuntu): status |
New |
Fix Released |
|
| 2010-02-19 21:32:55 |
Brian Murray |
removed subscriber Ubuntu Review Team |
|
|
|
| 2010-02-28 23:03:39 |
Mike Massonnet |
attachment added |
|
ruby-gnome2-gtk-threads-patch.debdiff http://launchpadlibrarian.net/39894438/ruby-gnome2-gtk-threads-patch.debdiff |
|
| 2010-02-28 23:04:45 |
Mike Massonnet |
attachment removed |
ruby-gnome2-gtk-thread-patch.debdiff http://launchpadlibrarian.net/39385299/ruby-gnome2-gtk-thread-patch.debdiff |
|
|
| 2010-06-29 13:14:52 |
Benjamin Drung |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2010-07-01 20:23:59 |
Martin Pitt |
ruby-gnome2 (Ubuntu Karmic): status |
New |
Fix Committed |
|
| 2010-07-01 20:24:04 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2010-07-01 20:24:08 |
Martin Pitt |
tags |
patch |
patch verification-needed |
|
| 2010-08-13 13:10:25 |
Jean-Baptiste Lallement |
description |
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en |
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
REGRESSION:
The only package that depends on ruby-gnome2 in karmic is alien-arena-browser, which is far from being a critical application. The impact of a potential regression would be very limited.
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
|
| 2010-08-13 13:20:50 |
Jean-Baptiste Lallement |
description |
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
REGRESSION:
The only package that depends on ruby-gnome2 in karmic is alien-arena-browser, which is far from being a critical application. The impact of a potential regression would be very limited.
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
|
| 2010-08-13 13:46:57 |
Jean-Baptiste Lallement |
description |
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
REGRESSION:
The following applications use libgtk2-ruby and threads: fantasdic-1.0beta7 geekast-0.1.3 kazehakase-0.5.8 mhc-0.25.1+20090120 rbbr-0.6.0 xnetcardconfig-0.2.1
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
|
| 2010-08-13 13:52:25 |
Jean-Baptiste Lallement |
description |
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
progress.pulse
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
REGRESSION:
The following applications use libgtk2-ruby and threads: fantasdic-1.0beta7 geekast-0.1.3 kazehakase-0.5.8 mhc-0.25.1+20090120 rbbr-0.6.0 xnetcardconfig-0.2.1
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
Binary package hint: libgtk2-ruby
In Ubuntu 9.10 with the version of libgtk2-ruby from the repositories (0.19.0), new threads cause the Gtk main loop to freeze. As an example, the following code will never produce any output:
===== Impact =====
I don't know which program available directly within Ubuntu is written in Ruby-GTK+, but those which do and which are using the Ruby Thread class are broken, and of course developing such a program is broken too.
The fix is available in ruby-gnome2 since version 0.19.2 and was introduced through SVN revisions 3692[1] and 3694[2]. Both are within the attachment "ruby-gnome2-gtk-thread-patch.debdiff" in comment #1.
[1] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3692
[2] http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2?view=rev&revision=3694
TEST CASE:
require 'gtk2'
Thread.new do
sleep 1 # Look busy
exit # Finished, exit
end
# Main loop
loop do
# Process all currently pending events
Gtk.main_iteration while Gtk.events_pending?
print '.'
end
However, when the latest version of the bindings is installed (0.19.3) the program works as expected, filling the screen with dots.
TEST CASE 2:
Here is another example for reproducing this bug:
require "gtk2"
include Gtk, GLib
# Create widgets
window = Window.new
vbox = VBox.new(false, 2)
button = Button.new("Run Thread")
progress = ProgressBar.new
# Pack widgets
window.add(vbox)
vbox.add(button)
vbox.add(progress)
# Set default window size
window.default_width = 120
window.default_height = 50
window.show_all
# Connect signals
button.signal_connect("clicked") do
Thread.new do
puts "Thread started!"
loop do
progress.pulse
sleep 1
end
end
end
window.signal_connect("destroy") { main_quit }
# Show all and run
main # start the GTK+ main loop
The test program shows a window with a button and a progress bar. Clicking the button will execute a Ruby Thread object, and the GUI visual elements/the GTK+ main loop will remain freezed.
REGRESSION:
The following applications use libgtk2-ruby and threads: fantasdic-1.0beta7 geekast-0.1.3 kazehakase-0.5.8 mhc-0.25.1+20090120 rbbr-0.6.0 xnetcardconfig-0.2.1
The example in the bug description is supposed to print dots, and instead it doesn't.
This problem is also reported at:
http://sourceforge.net/mailarchive/forum.php?thread_name=dc3bf8581001120746kb5da118udd0a74439cc4dcd9%40mail.gmail.com&forum_name=ruby-gnome2-devel-en
|
|
| 2010-08-13 14:07:14 |
Jean-Baptiste Lallement |
tags |
patch verification-needed |
patch verification-done |
|
| 2010-08-13 16:07:58 |
Launchpad Janitor |
ruby-gnome2 (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2011-05-19 11:48:18 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/ruby-gnome2 |
|
