GNOME Bugzilla – Bug 323778
gimp_edit_stroke fails when run non-interactivly
Last modified: 2008-01-15 13:03:13 UTC
Steps to reproduce: Run the following from the command line: gimp -i --batch "(script-fu-sota-chrome-logo -80 -47 0.75 \"fdsa\" 150 \"RoostHeavy\" \"/usr/share/gimp/2.0/scripts/images/beavis.jpg\" '(0 0 0) '(0 0 0))" "(gimp-quit 0)" Stack trace: (gimp:10357): Gimp-Paint-CRITICAL **: file gimppaintoptions.c: line 418 (gimp_paint_options_new): assertion `GIMP_IS_PAINT_INFO (paint_info)' failed (gimp:10357): Gimp-Core-CRITICAL **: file gimpcontext.c: line 1408 (gimp_context_define_properties): assertion `GIMP_IS_CONTEXT (context)' failed (gimp:10357): Gimp-Core-CRITICAL **: file gimpcontext.c: line 1326 (gimp_context_set_parent): assertion `GIMP_IS_CONTEXT (context)' failed (gimp:10357): GLib-GObject-CRITICAL **: file gobject.c: line 1579 (g_object_unref): assertion `G_IS_OBJECT (object)' failed (script-fu:10364): LibGimpBase-WARNING **: script-fu: wire_read(): error (script-fu:10363): LibGimpBase-WARNING **: script-fu: wire_read(): error Segmentation fault Other information: The sota chrome script of course runs fine when run interactivly, but seg- faults gimp when run from the command line. I'm fairly sure the crash happens in the gimp_edit_stoke call on line 141 of sota-chrome-logo.scm. Havn't tested with 2.2.9 but I don't see anything in the change log that makes me think this might have been fixed.
Fixed in both branches: 2005-12-11 Michael Natterer <mitch@gimp.org> * app/core/gimpstrokedesc.c (gimp_stroke_desc_new): fall back to the paintbrush if we can't get the paint method from the active tool (because there is no active tool). Fixes bug #323778.
You RULE! My bug got fixed within 8 hours!
*** Bug 324374 has been marked as a duplicate of this bug. ***