Daniel - there is that bug in gobject about GParamSpecs segfaulting I
mentioned in the gimp-devel thread - I don know if it is listed in
bugzilla - but if you are talking about a release "right now", I think
it'd be worth taking a look at.
Steps to reproduce:
$ python
Python 2.7.3 (default, Jul 24 2012, 11:41:40)
[GCC 4.6.3 20120306 (Red Hat 4.6.3-2)] on linux2
>>> from gi.repository import Gegl
>>> Gegl.init([])[]
>>> params = Gegl.operation_list_properties("gegl:png-load")
(python:21947): GEGL-gegl-operations.c-WARNING **: Adding
GeglChantinvert-linear_c shadows GeglChantinvert_c for operation
gegl:invert
/usr/lib64/python2.7/site-packages/gi/types.py:43: Warning:
g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed
return info.invoke(*args, **kwargs)
/usr/lib64/python2.7/site-packages/gi/types.py:43: Warning:
g_object_ref_sink: assertion 'G_IS_OBJECT (object)' failed
return info.invoke(*args, **kwargs)
** (python:21947): CRITICAL **: pygobject_register_wrapper: assertion
'PyObject_TypeCheck(self, &PyGObject_Type)' failed
>>> dir(params[0])
Segmentation fault (core dumped)
$
js
-><-
On 29 November 2013 11:21, Daniel Sabo <danielsabo@xxxxxxxxx> wrote:
> Gimp 2.8 still has "GEGL Operation" under the Tools menu, which
> apparently some people are using because we get bug reports about it
> crashing. I don't see the time it would take to backport those fixes
> to the 0.2 branch as worthwhile; there aren't any significant changes
> required for Gimp to use 0.3 but the fixes in GEGL are intertwined
> with other changes that make backporting impractical.
> _______________________________________________
> gegl-developer-list mailing list
> List address: gegl-developer-list@xxxxxxxxx
> List membership: https://mail.gnome.org/mailman/listinfo/gegl-developer-list
>
_______________________________________________
gegl-developer-list mailing list
List address: gegl-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gegl-developer-list
