[Gimp-developer] Gimp 2.3.1 crash
Hi, I havnt been able to run gimp since 2.3.1 (2.3.0 worked well - Apart from the useual development bugs) It always crashes on startup, even if I dont load data. But works if I load the gimp with no UI. Tried removing all the libgimp libs and my prefs for a fresh install but no good. GDB Says Program received signal SIGSEGV, Segmentation fault. 0xb7eecc2b in gimp_param_spec_rgb () from /usr/local/lib/libgimpcolor-2.0.so.0 Heres my output. /gimp-2.3.1 gimp (gimp:25314): GLib-GObject-WARNING **: cannot register existing type `GimpConfigInterface' (gimp:25314): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed (gimp:25314): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `g_type_parent (interface_type) == G_TYPE_INTERFACE' failed (gimp:25314): GLib-GObject-WARNING **: cannot register existing type `GimpConfigInterface' (gimp:25314): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed (gimp:25314): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `g_type_parent (interface_type) == G_TYPE_INTERFACE' failed (gimp:25314): GLib-GObject-WARNING **: cannot register existing type `GimpParamRGB' (gimp:25314): GLib-GObject-CRITICAL **: g_param_spec_internal: assertion `G_TYPE_IS_PARAM (param_type) param_type != G_TYPE_PARAM' failed Segmentation fault ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Akanna Menu patch
Hi, Kevin Cozens [EMAIL PROTECTED] writes: Most users will invoke items from the menu and won't care what carries out the action (ie. plug-in, or script) so I don't feel the menus should provide any such information. What would be useful is for the Procedural Browser to include the menu path as is currently done in the plug-in browser. The procedure browser is just that, a procedure browser. There is no point in adding a menu path there since a procedure doesn't necessarily have a menu path associated with it. This is functionality that the Menu Browser is supposed to offer. To provide some indication as to the origin of a plug-in or script listed in one of the browsers without cluttering the browser window it could be done via a word (or two?) in brackets at the end of the line which indcates the type of the entry. After Temporary Procedure or GIMP Plug-in you could have (in brackets) Core, Perl, Python, Script-Fu, or Tiny-Fu (for example). For plug-ins written in C adding a word in brackets at the end could be skipped. It may only be useful for items registered by scripting plug-ins. Sorry, but GIMP also doesn't know what language the procedure is written in. Such a framework would first have to be added and I don't see it as particularily useful. Sven ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 2.3.1 crash
Hi, Campbell Barton [EMAIL PROTECTED] writes: Hi, I havnt been able to run gimp since 2.3.1 (2.3.0 worked well - Apart from the useual development bugs) It always crashes on startup, even if I dont load data. But works if I load the gimp with no UI. Tried removing all the libgimp libs and my prefs for a fresh install but no good. You are running gimp-2.3 linked against the libraries from gimp-2.2 (or 2.0). Fix your linker setup. Sven ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 2.3.1 crash
Sven Neumann wrote: Campbell Barton writes: It always crashes on startup, even if I dont load data. But works if I load the gimp with no UI. Tried removing all the libgimp libs and my prefs for a fresh install but no good. You are running gimp-2.3 linked against the libraries from gimp-2.2 (or 2.0). Fix your linker setup. To elaborate a bit on what Sven has said: You can tell whether you're linking to the right GIMP libs by running ldd on the gimp-2.3 binary. If you're seeing libs like /usr/local/lib/gimp/2.0/libgimp-2.0.so or /usr/lib/gimp/2.0/libgimp-2.0.so instead of $prefix/lib/gimp/2.0/libgimp-2.0.so then you're linking to the wrong libraries. This could be because the directory where the older GIMP libraries are installed is in /etc/ld.so.conf - I seem to recall that this plays havoc with link-time linking (which libtool does) and definitely does with runtime linking. I'm not sure what the solution might be if you've installed an official 2.2 or 2.0 GIMP in /usr, and you want to install 2.3.1 in /usr/local or /some/special/prefix - perhaps someone else can give ideas how to get around that problem. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] Lyon, France ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: Akanna Menu patch
On 6/11/05, Sven Neumann [EMAIL PROTECTED] wrote: Sorry, but GIMP also doesn't know what language the procedure is written in. Such a framework would first have to be added and I don't see it as particularily useful. It's a great solution for the real world problem of : Run the Foo plugin. I don't have the Foo plugin. Oh crap, what package is it in? Rockwalrus ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 2.3.1 crash
On 6/11/05, David Neary [EMAIL PROTECTED] wrote: This could be because the directory where the older GIMP libraries are installed is in /etc/ld.so.conf - I seem to recall that this plays havoc with link-time linking (which libtool does) and definitely does with runtime linking. I'm not sure what the solution might be if you've installed an official 2.2 or 2.0 GIMP in /usr, and you want to install 2.3.1 in /usr/local or /some/special/prefix - perhaps someone else can give ideas how to get around that problem. the 2.2 libraries can be in /etc/ld.so.conf's path, but the 2.3 cannot be. $ ldd `which gimp` libgimpwidgets-2.0.so.0 = /usr/lib/libgimpwidgets-2.0.so.0 (0x4003) libgimpmodule-2.0.so.0 = /usr/lib/libgimpmodule-2.0.so.0 (0x4010e000) etc.. $ ldd `which gimp-2.3` libgimpwidgets-2.0.so.0 = /usr/unstable/lib/libgimpwidgets-2.0.so.0 (0x40018000) libgimpmodule-2.0.so.0 = /usr/unstable/lib/libgimpmodule-2.0.so.0 (0x40106000) where /usr/lib is always in the ldconfig path, and /usr/unstable/lib is most definitely not. Rockwalrus ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
