You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(6) |
Sep
(16) |
Oct
(36) |
Nov
(85) |
Dec
(151) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(49) |
Feb
(51) |
Mar
(71) |
Apr
(87) |
May
(91) |
Jun
(93) |
Jul
(160) |
Aug
(229) |
Sep
(85) |
Oct
(89) |
Nov
(85) |
Dec
(98) |
| 2004 |
Jan
(40) |
Feb
(98) |
Mar
(149) |
Apr
(106) |
May
(153) |
Jun
(77) |
Jul
(85) |
Aug
(55) |
Sep
(50) |
Oct
(53) |
Nov
(83) |
Dec
(32) |
| 2005 |
Jan
(97) |
Feb
(124) |
Mar
(60) |
Apr
(79) |
May
(55) |
Jun
(62) |
Jul
(70) |
Aug
(130) |
Sep
(115) |
Oct
(32) |
Nov
(46) |
Dec
(54) |
| 2006 |
Jan
(114) |
Feb
(78) |
Mar
(37) |
Apr
(54) |
May
(82) |
Jun
(34) |
Jul
(54) |
Aug
(50) |
Sep
(26) |
Oct
(46) |
Nov
(105) |
Dec
(83) |
| 2007 |
Jan
(105) |
Feb
(64) |
Mar
(57) |
Apr
(20) |
May
(18) |
Jun
(80) |
Jul
(108) |
Aug
(26) |
Sep
(36) |
Oct
(49) |
Nov
(94) |
Dec
(46) |
| 2008 |
Jan
(24) |
Feb
(24) |
Mar
(200) |
Apr
(92) |
May
(112) |
Jun
(54) |
Jul
(41) |
Aug
(50) |
Sep
(66) |
Oct
(82) |
Nov
(15) |
Dec
(44) |
| 2009 |
Jan
(68) |
Feb
(34) |
Mar
(55) |
Apr
(50) |
May
(95) |
Jun
(33) |
Jul
(24) |
Aug
(40) |
Sep
(61) |
Oct
(33) |
Nov
(7) |
Dec
(61) |
| 2010 |
Jan
(18) |
Feb
(47) |
Mar
(24) |
Apr
(24) |
May
(42) |
Jun
(59) |
Jul
(28) |
Aug
(23) |
Sep
(55) |
Oct
(102) |
Nov
(33) |
Dec
(11) |
| 2011 |
Jan
(37) |
Feb
(115) |
Mar
(96) |
Apr
(37) |
May
(8) |
Jun
(13) |
Jul
(7) |
Aug
(61) |
Sep
(143) |
Oct
(78) |
Nov
(14) |
Dec
(33) |
| 2012 |
Jan
(49) |
Feb
(57) |
Mar
(62) |
Apr
(38) |
May
(26) |
Jun
(16) |
Jul
(12) |
Aug
(10) |
Sep
(8) |
Oct
(12) |
Nov
(38) |
Dec
(25) |
| 2013 |
Jan
(55) |
Feb
(53) |
Mar
(39) |
Apr
(37) |
May
(21) |
Jun
(4) |
Jul
(7) |
Aug
(8) |
Sep
(24) |
Oct
(17) |
Nov
(11) |
Dec
(81) |
| 2014 |
Jan
(22) |
Feb
(9) |
Mar
(29) |
Apr
(133) |
May
(12) |
Jun
(13) |
Jul
(5) |
Aug
(11) |
Sep
|
Oct
(10) |
Nov
(18) |
Dec
(1) |
| 2015 |
Jan
(18) |
Feb
(2) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(28) |
Oct
(15) |
Nov
(8) |
Dec
(7) |
| 2016 |
Jan
(19) |
Feb
|
Mar
|
Apr
(1) |
May
(10) |
Jun
(3) |
Jul
(19) |
Aug
|
Sep
(5) |
Oct
(1) |
Nov
(9) |
Dec
|
| 2017 |
Jan
|
Feb
(18) |
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(2) |
Dec
|
|
From: Detlef R. <det...@gm...> - 2016-05-12 18:15:43
|
Hi,
Am 12.05.2016 um 16:06 schrieb cedlemo:
> > this may be completely the wrong list,
> This list is more related to the ruby-gnome2 bindings and its support.
>
> > but may be someone can help
> but I am curious so I will try to help you
>
> Can you give informations:
>
> which debian
testing
> Gtk version
3.20.3
> Desktop (Gnome, Xfce) and version
Xfce 4.12
> theme used.
Adwaita, Gilouche and "high contrast" show the problem.
> Is the problem specific for an application you created
It is a special purpose widget, something like a Gtk::Notebook with
grouped tabs. If other applications have the same problem, I don't know.
But the widget may be very specific.
> Have you/use you a custom Css configuration?.
The specific part of the css file I already posted with my last mail.
Here is a small example, that shows the problem on my system.
#!/usr/bin/env ruby
require "gtk3"
provider = Gtk::CssProvider.new
css = <<-CSS
@define-color frame_border_tabs rgb(70%, 70%, 70%);
@define-color transparent rgba(0, 0, 0, 0.0);
frame#tabs {
border-style: solid;
border-color: @frame_border_tabs @transparent @frame_border_tabs
@frame_border_tabs;
border-width: 0.2em 0.32em 0.05em 0.1em;
border-radius: 1.2em 0.7em 0.7em 1.2em;
padding: 0.25em 0.25em 0.25em 0.25em;
}
CSS
provider.load :data => css
screen = Gdk::Display.default.default_screen
Gtk::StyleContext.add_provider_for_screen(screen,
provider,
Gtk::StyleProvider::PRIORITY_USER)
window = Gtk::Window.new
frame = Gtk::Frame.new
window << frame
label = Gtk::Label.new 'Content'
frame << label
frame.name = 'tabs'
frame.style_context.add_provider provider, GLib::MAXUINT
window.show_all
window.signal_connect "destroy" do
Gtk.main_quit
end
Gtk.main
Thanks, detlef
>
>
> Cedlemo
>
> On 11/05/2016 20:53, Detlef Reichl wrote:
>> Hi,
>>
>> this may be completely the wrong list, but may be someone can help :-)
>>
>>
>> I have a Gtk::Frame which is styled with CSS.This is the relevant part
>> of the css file:
>>
>> frame#tabs {
>> border-style: solid;
>> border-color: @frame_border_tabs @transparent @frame_border_tabs
>> @frame_border_tabs;
>> border-width: 0.2em 0.32em 0.05em 0.1em;
>> border-radius: 1.2em 0.7em 0.7em 1.2em;
>> padding: 0.25em 0.25em 0.25em 0.25em;
>> }
>>
>>
>> It is drawn as in the attached image. The outer rounded border is like
>> expected. The rectangular one should from my point of view not be
>> visible. And before the CSS changes of gtk it was not. Is it also a
>> new behavior, where I have to change my css / code? It also _now_
>> seems to be theme dependent. Before the changes with the same theme it
>> worked as expected. The _problematic_ theme is Xfce-4.6 from debian
>> testing.
>>
>> detlef
>>
>>
>> ------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of MDM
>> restrictions. Mobile Device Manager Plus allows you to control only the
>> apps on BYO-devices by containerizing them, leaving personal data untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>>
>>
>> _______________________________________________
>> ruby-gnome2-devel-en mailing list
>> rub...@li...
>> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> ruby-gnome2-devel-en mailing list
> rub...@li...
> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
>
|
|
From: cedlemo <ce...@gm...> - 2016-05-12 14:06:34
|
> this may be completely the wrong list,
This list is more related to the ruby-gnome2 bindings and its support.
> but may be someone can help
but I am curious so I will try to help you
Can you give informations:
which debian
Gtk version
Desktop (Gnome, Xfce) and version
theme used.
Is the problem specific for an application you created
Have you/use you a custom Css configuration?.
Cedlemo
On 11/05/2016 20:53, Detlef Reichl wrote:
> Hi,
>
> this may be completely the wrong list, but may be someone can help :-)
>
>
> I have a Gtk::Frame which is styled with CSS.This is the relevant part
> of the css file:
>
> frame#tabs {
> border-style: solid;
> border-color: @frame_border_tabs @transparent @frame_border_tabs
> @frame_border_tabs;
> border-width: 0.2em 0.32em 0.05em 0.1em;
> border-radius: 1.2em 0.7em 0.7em 1.2em;
> padding: 0.25em 0.25em 0.25em 0.25em;
> }
>
>
> It is drawn as in the attached image. The outer rounded border is like
> expected. The rectangular one should from my point of view not be
> visible. And before the CSS changes of gtk it was not. Is it also a
> new behavior, where I have to change my css / code? It also _now_
> seems to be theme dependent. Before the changes with the same theme it
> worked as expected. The _problematic_ theme is Xfce-4.6 from debian
> testing.
>
> detlef
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>
>
> _______________________________________________
> ruby-gnome2-devel-en mailing list
> rub...@li...
> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
|
|
From: Detlef R. <det...@gm...> - 2016-05-11 19:07:50
|
Hi,
this may be completely the wrong list, but may be someone can help :-)
I have a Gtk::Frame which is styled with CSS.This is the relevant part
of the css file:
frame#tabs {
border-style: solid;
border-color: @frame_border_tabs @transparent @frame_border_tabs
@frame_border_tabs;
border-width: 0.2em 0.32em 0.05em 0.1em;
border-radius: 1.2em 0.7em 0.7em 1.2em;
padding: 0.25em 0.25em 0.25em 0.25em;
}
It is drawn as in the attached image. The outer rounded border is like
expected. The rectangular one should from my point of view not be
visible. And before the CSS changes of gtk it was not. Is it also a new
behavior, where I have to change my css / code? It also _now_ seems to
be theme dependent. Before the changes with the same theme it worked as
expected. The _problematic_ theme is Xfce-4.6 from debian testing.
detlef
|
|
From: Detlef R. <det...@gm...> - 2016-05-11 15:50:06
|
Hi cedlemo,
that works. Thank you!
detlef
Am 11.05.2016 um 11:00 schrieb cedlemo:
> Hi Detlef,
>
> this is related to some change in gtk3 try this
> label { color: red; };
>
> instead of
> GtkLabel { color: red};
>
> in the same way instead of using GtkGrid for example use grid.
> look here : https://developer.gnome.org/gtk3/stable/chap-css-overview.html
> the documentation has been updated
>
> regards
>
> cedlemo
> https://github.com/cedlemo
>
>
> On 10/05/2016 20:47, Detlef Reichl wrote:
>> Hi,
>>
>> CSS styling is not working for me since, i think, round a week. A self
>> written application does not show any CSS styling since then anymore.
>> And also the demo from cedlemo, which he posted in the gtk forums - see
>> below - only show black text, while it should show red one. ruby gnome
>> and rcairo are with the current git master and the system is debian testing.
>>
>> Could someone confirm this?
>>
>> detlef
>>
>>
>>
>> #!/usr/bin/env ruby
>> require "gtk3"
>>
>> provider = Gtk::CssProvider.new
>> provider.load(:data => "GtkLabel { color: red;}")
>>
>> screen = Gdk::Display.default.default_screen
>> Gtk::StyleContext.add_provider_for_screen(screen,
>> provider,
>>
>> Gtk::StyleProvider::PRIORITY_USER)
>>
>> window = Gtk::Window.new
>> window.title = "Simple example"
>> window.set_default_size(300, 300)
>>
>> label = Gtk::Label.new("Red text")
>> window.add(label)
>>
>> window.show_all
>> window.signal_connect "destroy" do
>> Gtk.main_quit
>> end
>> Gtk.main
>>
>> ------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of MDM
>> restrictions. Mobile Device Manager Plus allows you to control only the
>> apps on BYO-devices by containerizing them, leaving personal data untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>> _______________________________________________
>> ruby-gnome2-devel-en mailing list
>> rub...@li...
>> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> ruby-gnome2-devel-en mailing list
> rub...@li...
> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
>
|
|
From: cedlemo <ce...@gm...> - 2016-05-11 09:32:01
|
> And also the demo from cedlemo, which he posted in the gtk forums I have updated the demo in the gtk forums. Thanks cedlemo https://github.com/cedlemo |
|
From: cedlemo <ce...@gm...> - 2016-05-11 09:00:52
|
Hi Detlef,
this is related to some change in gtk3 try this
label { color: red; };
instead of
GtkLabel { color: red};
in the same way instead of using GtkGrid for example use grid.
look here : https://developer.gnome.org/gtk3/stable/chap-css-overview.html
the documentation has been updated
regards
cedlemo
https://github.com/cedlemo
On 10/05/2016 20:47, Detlef Reichl wrote:
> Hi,
>
> CSS styling is not working for me since, i think, round a week. A self
> written application does not show any CSS styling since then anymore.
> And also the demo from cedlemo, which he posted in the gtk forums - see
> below - only show black text, while it should show red one. ruby gnome
> and rcairo are with the current git master and the system is debian testing.
>
> Could someone confirm this?
>
> detlef
>
>
>
> #!/usr/bin/env ruby
> require "gtk3"
>
> provider = Gtk::CssProvider.new
> provider.load(:data => "GtkLabel { color: red;}")
>
> screen = Gdk::Display.default.default_screen
> Gtk::StyleContext.add_provider_for_screen(screen,
> provider,
>
> Gtk::StyleProvider::PRIORITY_USER)
>
> window = Gtk::Window.new
> window.title = "Simple example"
> window.set_default_size(300, 300)
>
> label = Gtk::Label.new("Red text")
> window.add(label)
>
> window.show_all
> window.signal_connect "destroy" do
> Gtk.main_quit
> end
> Gtk.main
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> ruby-gnome2-devel-en mailing list
> rub...@li...
> https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en
|
|
From: Detlef R. <det...@gm...> - 2016-05-10 19:01:28
|
Hi,
CSS styling is not working for me since, i think, round a week. A self
written application does not show any CSS styling since then anymore.
And also the demo from cedlemo, which he posted in the gtk forums - see
below - only show black text, while it should show red one. ruby gnome
and rcairo are with the current git master and the system is debian testing.
Could someone confirm this?
detlef
#!/usr/bin/env ruby
require "gtk3"
provider = Gtk::CssProvider.new
provider.load(:data => "GtkLabel { color: red;}")
screen = Gdk::Display.default.default_screen
Gtk::StyleContext.add_provider_for_screen(screen,
provider,
Gtk::StyleProvider::PRIORITY_USER)
window = Gtk::Window.new
window.title = "Simple example"
window.set_default_size(300, 300)
label = Gtk::Label.new("Red text")
window.add(label)
window.show_all
window.signal_connect "destroy" do
Gtk.main_quit
end
Gtk.main
|
|
From: cedlemo <ce...@gm...> - 2016-04-06 09:52:14
|
the Ruby-GNOME2 3.0.8 has been released, This new version of the Ruby-GNOME2 mainly improves GTK+ 3 support. An exhaustive list of the changes can be found on the project site : http://ruby-gnome2.osdn.jp/?News_20160404_1 or on the github repository of the project: https://github.com/ruby-gnome2/ruby-gnome2/blob/master/NEWS |
|
From: Kouhei S. <ko...@co...> - 2016-01-24 11:18:56
|
Hi, In <CAG...@ma...> "[ruby-gnome2-devel-en] NotImplementedError: TODO: GIArgument(array)[c][gdouble] -> Ruby" on Sun, 24 Jan 2016 10:11:37 +0000, jc...@gm... wrote: > Hi all, I'm seeing an unimplemented error when I try to read an array > of double from an object: > > NotImplementedError: TODO: GIArgument(array)[c][gdouble] -> Ruby > from /home/john/packages/gems/gems/gobject-introspection-3.0.7/lib/gobject-introspection/loader.rb:551:in > `invoke' > > Could this feature be added? > > I'm happy to try to make a patch if someone can point me towards the > bits of code that need writing. array_c_to_ruby_sized() in gobject-introspection/ext/gobject-introspection/rb-gi-argument.c will help you: https://github.com/ruby-gnome2/ruby-gnome2/blob/master/gobject-introspection/ext/gobject-introspection/rb-gi-argument.c#L153 Thanks, -- kou |
|
From: <jc...@gm...> - 2016-01-24 10:12:23
|
Hi all, I'm seeing an unimplemented error when I try to read an array
of double from an object:
NotImplementedError: TODO: GIArgument(array)[c][gdouble] -> Ruby
from /home/john/packages/gems/gems/gobject-introspection-3.0.7/lib/gobject-introspection/loader.rb:551:in
`invoke'
Could this feature be added?
I'm happy to try to make a patch if someone can point me towards the
bits of code that need writing.
John
|
|
From: Kouhei S. <ko...@co...> - 2016-01-23 04:26:23
|
Hi, Thanks for your report. In <56A...@gm...> "[ruby-gnome2-devel-en] Gtk::TreeIter and Model missing method and name change" on Fri, 22 Jan 2016 20:23:21 +0100, Detlef Reichl <det...@gm...> wrote: > with Gtk3 gi bindings the Gtk::TreeIter#first_child method is missing. > Does Gtk::TreeIter.nth_child(0) exactly the same? Yes. Anyway, we should also provide Gtk::TreeIter#first_child in gi bindings: https://github.com/ruby-gnome2/ruby-gnome2/issues/682 > Also the Gtk::TreePath#up! and #down! methods are changed to > Gtk::TreePath#up and down. Is that intended? It's not intended. They should have !: https://github.com/ruby-gnome2/ruby-gnome2/issues/683 Thanks, -- kou |
|
From: Detlef R. <det...@gm...> - 2016-01-22 19:23:30
|
Hi, with Gtk3 gi bindings the Gtk::TreeIter#first_child method is missing. Does Gtk::TreeIter.nth_child(0) exactly the same? Also the Gtk::TreePath#up! and #down! methods are changed to Gtk::TreePath#up and down. Is that intended? Cheers, detlef |
|
From: <jc...@gm...> - 2016-01-18 14:35:41
|
In case anyone else is getting strange crashes, I've found a
work-around. I just disable the GC during introspection.
All introspection code is wrapped in:
gc_was_enabled = GC.disable
begin
result = do_some_introspection
ensure
if gc_was_enabled
GC.enable
end
end
and my crashes have gone away. Phew!
John
|
|
From: Kouhei S. <ko...@co...> - 2016-01-09 13:56:21
|
Hi, In <145...@ss...> "Re: [ruby-gnome2-devel-en] Crashes when cairo is compiled with xlib-xcb xcb options" on Fri, 08 Jan 2016 21:04:33 +0100, Stefan Salewski <ma...@ss...> wrote: > @surf = @darea.window.create_similar_surface(Cairo::CONTENT_COLOR_ALPHA, @darea.allocation.width + 2 * $OFFSET, @darea.allocation.height + 2 * $OFFSET) > > creates the background surface without need for a intermediate cairo > context and seems to work without crashes! Good! Alternatively, adding "other.destroy" may fix the crash: @surf = other.create_similar(Cairo::CONTENT_COLOR_ALPHA, @darea.allocation.width + 2 * $OFFSET, @darea.allocation.height + 2 * $OFFSET) other.destroy Thanks, -- kou |
|
From: Stefan S. <ma...@ss...> - 2016-01-08 20:04:41
|
On Fri, 2016-01-08 at 20:40 +0100, Stefan Salewski wrote: > I will see if I can replace this call. Done! @surf = @darea.window.create_similar_surface(Cairo::CONTENT_COLOR_ALPHA, @darea.allocation.width + 2 * $OFFSET, @darea.allocation.height + 2 * $OFFSET) creates the background surface without need for a intermediate cairo context and seems to work without crashes! But currently my whole Ruby system is all compiled with -O0 and full debugging enabled, I have to recompile and test with full speed still. Thanks for your support, Stefan Salewski |
|
From: Stefan S. <ma...@ss...> - 2016-01-08 19:40:40
|
On Mon, 2016-01-04 at 21:38 +0900, Kouhei Sutou wrote:
> It seems that your cairo XCB surface is destroyed twice.
Have tried to debug it with gdb, but without real success.
Yesterday I tried to comment out parts of my code. My current feeling is
that
I have in pet-canvas.rb
@darea.signal_connect('configure-event') { darea_configure_callback }
darea_configure_callback() calls function paint(), where I have
cr0 = @darea.window.create_cairo_context
If I comment out that line, the bug is gone. But I need that to create a
similar surface for my background pattern!
I have no idea why that may generate the crash, why only with xcb, and
why not when I have moved some elements on my schematic sheet.
I will see if I can replace this call. For the draw event it is easy to
replace, I get the cairo context as a parameter for the called block. I
really should replace that. But for configure-event that is not that
easy. My intent was to create a similar surface for maximum performance,
and I think for that I need a cairo context. But a plain image surface
may work for testing.
|
|
From: Stefan S. <ma...@ss...> - 2016-01-06 15:08:03
|
On Wed, 2016-01-06 at 15:38 +0100, Stefan Salewski wrote: > Hello, > > what really is strange: > > When I put GC.disable in file peted.rb here > > > end # module PetEd > > GC.disable > > options = Hash.new > This is the debugger log when GC is dissabled: http://ssalewski.de/tmp/log.txt |
|
From: Stefan S. <ma...@ss...> - 2016-01-06 14:38:57
|
On Mon, 2016-01-04 at 19:04 +0100, Stefan Salewski wrote: > > The code is still exactly the same as in > > http://ssalewski.de/pet20150928.tar > > I had no spare time since then to work on it. > > At the end of peted.rb there is no exception, only plain > > Gtk.main > > at the end. > > And for termination of the program there is > > self.signal_connect('destroy') {Gtk.main_quit} > > in file peted.rb > > > Hello, what really is strange: When I put GC.disable in file peted.rb here end # module PetEd GC.disable options = Hash.new I get the same crash when I immediately terminate the program after startup. So may the bug exist in Cairo C lib itself? Well, Gmome is using Cairo too, gschem too, all seems to be OK. But maybe my Ruby code calls something of Cairo C lib what is buggy? I think there are some Linux Window managers out there which use XCB, so some people may have Cairo compiled with XCB unfortunately. |
|
From: Stefan S. <ma...@ss...> - 2016-01-04 18:04:10
|
On Mon, 2016-01-04 at 21:38 +0900, Kouhei Sutou wrote:
>
> It seems that your cairo XCB surface is destroyed twice.
> It may be caused by Ruby's sweep (in GC) timing. Ruby script
> can't control object order to be swept.
>
>
> It seems that your script was finished by exception.
> Could you confirm that your script raises any exception?
>
> For example:
>
> ---
> # ...
>
> begin
> Gtk.main
> rescue Exception
> puts "#{$!.class}: #{$!}"
> puts $@
> end
> ---
>
>
The code is still exactly the same as in
http://ssalewski.de/pet20150928.tar
I had no spare time since then to work on it.
At the end of peted.rb there is no exception, only plain
Gtk.main
at the end.
And for termination of the program there is
self.signal_connect('destroy') {Gtk.main_quit}
in file peted.rb
|
|
From: Kouhei S. <ko...@co...> - 2016-01-04 12:38:10
|
Hi, In <145...@ss...> "Re: [ruby-gnome2-devel-en] Crashes when cairo is compiled with xlib-xcb xcb options" on Sun, 03 Jan 2016 20:45:24 +0100, Stefan Salewski <ma...@ss...> wrote: > On Mon, 2016-01-04 at 00:11 +0900, Kouhei Sutou wrote: >> Could you get C level backtrace? >> >> segv-handler-gdb gem will help you: > > This is my first attempt to debug, is it helpful for you? > > http://ssalewski.de/tmp/debug.txt Thanks. It seems that your cairo XCB surface is destroyed twice. It may be caused by Ruby's sweep (in GC) timing. Ruby script can't control object order to be swept. It seems that your script was finished by exception. Could you confirm that your script raises any exception? For example: --- # ... begin Gtk.main rescue Exception puts "#{$!.class}: #{$!}" puts $@ end --- Thanks, -- kou |
|
From: Stefan S. <ma...@ss...> - 2016-01-03 19:45:35
|
On Mon, 2016-01-04 at 00:11 +0900, Kouhei Sutou wrote: > Could you get C level backtrace? > > segv-handler-gdb gem will help you: This is my first attempt to debug, is it helpful for you? http://ssalewski.de/tmp/debug.txt |
|
From: Kouhei S. <ko...@co...> - 2016-01-03 15:11:17
|
Hi, In <145...@ss...> "[ruby-gnome2-devel-en] Crashes when cairo is compiled with xlib-xcb xcb options" on Sun, 03 Jan 2016 15:19:58 +0100, Stefan Salewski <ma...@ss...> wrote: > cairo-1.14.6 was compiled with that options on my Gentoo AMD64 Linux > box, and I discovered yesterday that my program > http://ssalewski.de/PetEd.html.en crashed when I started it with command > "ruby peted.rb" and immediately closed that empty window by clicking the > cross on top right corner. Could you get C level backtrace? segv-handler-gdb gem will help you: https://github.com/kou/segv-handler-gdb % gem install segv-handler-gdb % ruby -rsegv-handler-gdb peted.rb (crashed) % ls /tmp/segv-handler-gdb* Thanks, -- kou |
|
From: Stefan S. <ma...@ss...> - 2016-01-03 14:39:22
|
Dear Mr Kouhei Sutou, have you ever tested rcairo for cairo library compiled with xlib-xcb xcb support? cairo-1.14.6 was compiled with that options on my Gentoo AMD64 Linux box, and I discovered yesterday that my program http://ssalewski.de/PetEd.html.en crashed when I started it with command "ruby peted.rb" and immediately closed that empty window by clicking the cross on top right corner. That is for ruby-gnome2-3.0.7, ruby 2.2 and GTK 3.16. I had no idea about the crash (segmentation fault). I tested cairo -pong.rb, that works fine. Now I recompiled cairo without xlib-xcb xcb options, and crash is gone. That is not a big problem for me currently, my program is still unfinished and I can use cairo without lib-xcb xcb. Later, if other people may use my program with lib-xcb xcb enabled it may be a problem. Of course my program may have a serious bug. But I wonder why the crash occurs only with cairo options lib-xcb xcb. And just clicking the cross on top right corner direct after startup is a simple operation, there is no code which is executed in my program. I have noticed that I can avoid the crash when I start it with a file argument like "ruby peted.rb test.sch" and move some symbols around before terminating the program. And generally the program seems to work the same with and without cairo options lib-xcb xcb. Problem is only termination, but debugging that is really difficult. Best regards, Stefan Salewski |
|
From: Detlef R. <det...@gm...> - 2016-01-02 10:02:08
|
Hi, On 02.01.2016 01:54, Ra...@la... wrote: > I did > notice that the last change to the project was to add that file that is > failing in your environment (sample/gtk-demo/search_entry2.rb). for strange reasons the sample/gtk-demo/search_entry2.rb file was not copied to the pkg directory while rake gem:build. rm -rf pkg and start the rake task again did it. Thanks, detlef |
|
From: <Ra...@la...> - 2016-01-02 00:55:04
|
So I just tried again and was able to build the latest code. I did notice that the last change to the project was to add that file that is failing in your environment (sample/gtk-demo/search_entry2.rb). I did get a lot of warnings about the gem description and summary being identical for each gem that was built. I tried with both ruby 2.2.1 and 2.2.3. Maybe the problems are caused by the versions of rake and/or gem? Here is what I'm running: $ gem --version 2.4.8 $ rake --version rake, version 10.4.2 $ rvm --version rvm 1.26.11 (latest) by Wayne E. Seguin <way...@gm...>, Michal Papis <mp...@gm...> [https://rvm.io/] $ uname -a Linux ubuntu 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Jon From: Detlef Reichl <det...@gm...> To: rub...@li... Date: 01/01/2016 01:16 PM Subject: [ruby-gnome2-devel-en] rake gem:build fails Hi, on a fresh check out of ruby-gnome "rake gem:build" fails with the following error message: det@datengrab:~/Schreibtisch/soft/ruby-gnome2$ rake --trace gem:build ** Invoke gem:build (first_time) ** Execute gem:build /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem /usr/bin/ruby2.2 -S rake gem cd pkg/gtk3-3.0.7 WARNING: See http://guides.rubygems.org/specification-reference/ for help rake aborted! Gem::InvalidSpecificationException: ["sample/gtk-demo/search_entry2.rb"] are not files Tasks: TOP => gem => pkg/gtk3-3.0.7.gem (See full trace by running task with --trace) rake aborted! Command failed with status (1): [/usr/bin/ruby2.2 -S rake gem...] /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:66:in `block in create_shell_runner' /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:57:in `call' /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:57:in `sh' /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:37:in `sh' /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:94:in `ruby' /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:37:in `ruby' /home/det/Schreibtisch/soft/ruby-gnome2/Rakefile:355:in `block (4 levels) in <top (required)>' /home/det/Schreibtisch/soft/ruby-gnome2/Rakefile:354:in `chdir' /home/det/Schreibtisch/soft/ruby-gnome2/Rakefile:354:in `block (3 levels) in <top (required)>' /home/det/Schreibtisch/soft/ruby-gnome2/Rakefile:353:in `each' /home/det/Schreibtisch/soft/ruby-gnome2/Rakefile:353:in `block (2 levels) in <top (required)>' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `call' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `block in execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `each' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:179:in `block in invoke_with_call_chain' /usr/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize' /usr/lib/ruby/vendor_ruby/rake/task.rb:172:in `invoke_with_call_chain' /usr/lib/ruby/vendor_ruby/rake/task.rb:165:in `invoke' /usr/lib/ruby/vendor_ruby/rake/application.rb:150:in `invoke_task' /usr/lib/ruby/vendor_ruby/rake/application.rb:106:in `block (2 levels) in top_level' /usr/lib/ruby/vendor_ruby/rake/application.rb:106:in `each' /usr/lib/ruby/vendor_ruby/rake/application.rb:106:in `block in top_level' /usr/lib/ruby/vendor_ruby/rake/application.rb:115:in `run_with_threads' /usr/lib/ruby/vendor_ruby/rake/application.rb:100:in `top_level' /usr/lib/ruby/vendor_ruby/rake/application.rb:78:in `block in run' /usr/lib/ruby/vendor_ruby/rake/application.rb:176:in `standard_exception_handling' /usr/lib/ruby/vendor_ruby/rake/application.rb:75:in `run' /usr/bin/rake:27:in `<main>' Tasks: TOP => gem:build $ uname -a Linux datengrab 4.3.0-1-amd64 #1 SMP Debian 4.3.3-2 (2015-12-17) x86_64 GNU/Linux $ ruby --version ruby 2.2.3p173 (2015-08-18) [x86_64-linux-gnu] Cheers detlef ------------------------------------------------------------------------------ _______________________________________________ ruby-gnome2-devel-en mailing list rub...@li... https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en |