GNOME Bugzilla – Bug 110227
GIMP segfaults on startup
Last modified: 2003-04-16 08:52:09 UTC
$ gimp-1.3 gimp-1.3: fatal error: Segmentation fault gimp-1.3 (pid:10977): [E]xit, [H]alt, show [S]tack trace or [P]roceed: h (script-fu:11130): LibGimpBase-WARNING **: script-fu: wire_read(): error # gcc -v Reading specs from /usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.00/3.2/specs Configured with: ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure Thread model: posix gcc version 3.2 CFLAGS= -O2 -g -pipe -mschedule=8000 -mpa-risc-2-0 -I/usr/local/include -I/opt/gnome/include -L/usr/local/lib -L/opt/gnome/lib What other data you need????
This doesn't look like Script-Fu crashing, but GIMP crashing. First of all, you should update to a more recent version. Then, please provide a stack trace of the crash.
It would be nice if you could let us know if you had more luck with 1.3.13.
Gimp 1.3.13 behaves the same way, no luck. I don't know how to get a stack trace, I could not use the option [S], nothing is displayed and I have to kill -9 the process. Perhaps you can tell me another way. Thx PS: the gcc I'm using compiles only to 32bits executables
If you want to get a stack trace, you should have gdb installed. Are you sure that the debugger is installed and is in your path? You should also start the GIMP with the option "--enable-stack-trace always" so that it generates the stack trace immediately instead of asking you if you want one or not.
Now that I think about it, you could also generate the stack trace yourself without waiting for the GIMP to call gdb. If the GIMP is still running (you mentioned that you have to kill it yourself), you can check its process id and then run gdb like this: gdb /path/to/gimp <pid> (where <pid> is the process id of the GIMP) When you get the gdb prompt, type "bt" or "where" to get the stack trace.
Even simpler: run gimp in a debugger. If you use gdb, start gimp using 'gdb gimp-1.3'. At the gdb prompt, type r (for 'run'). When it crashes, type 'bt' (for 'backtrace') and paste the output here.
Thx, I will do that tomorrow.
Well, I found a report on a bug in HP-UX linker, patched and now I can start gimp!!! But hen I run a scriptFu I get the same error, but with a font config warning, any Ideas??? matias@trutien:~$ /opt/garnome/bin/gimp-1.3 (gimp-1.3:20078): Gtk-WARNING **: Can not open Input Method module file '/opt/garnome/etc/gtk-2.0/gtk.immodules': No such file or directory (script-fu:20081): Gtk-WARNING **: Can not open Input Method module file '/opt/garnome/etc/gtk-2.0/gtk.immodules': No such file or directory Fontconfig error: Cannot load default config file No fonts found; this probably means that the fontconfig library is not correctly configured. You may need to edit the fonts.conf configuration file. More information about fontconfig can be found in the fontconfig(3) manual page and on http://fontconfig.org (script-fu:20081): LibGimpBase-WARNING **: script-fu: wire_read(): error
fontconfig should have installed a default fonts.conf (usually found at /etc/fonts/fonts.conf). Please make sure that a valid font configuration is available.
Fixed the fontconfig issue all I can use scriptFu!!!! The sphere test does not work, but It not seems important Thx
Since the primary problem seems to have been caused by a linker bug, I'm closing this report as NOTGNOME.