GNOME Bugzilla – Bug 126645
Memory fault at start up.
Last modified: 2003-11-11 19:05:09 UTC
When lauching gimp, I get a memory fault at the end of the start up process. It is recoverable after hitting the key p as Proceed. It may be due to a faulty installation?! I do not know. It would be nice that Gimp gives a clean error message. If requested, I may try to use gdb and give the exact stack. Anyway, Gimp seems to be working fine afterwards.
Yes, please, a stack trace would be appreciated, since it might help us track down the problem. When this happens the next time, hit S rather than P, and attach the resulting text here. Thank you. Dave.
You are probably hitting the infamous freetype2 bug. Try if upgrading freetype2 fixes it. Or try if reducing your font setup to a small set of truetype fonts helps. If you use the CVS version, you could also try the --no-fonts command-line option.
That would be the first time I ever heard that pressing [P] for Proceed would get you anywhere. Usually there's no way to recover after a segmentation fault.
Unless the segfault is in the query function of a plug-in... if a plug-in segfaults, the core should keep on ticking. Whether he hits E or P is irrelevant, probably. Cheers, Dave.
well, I expected the user to be able to notice the difference between a crashing plug-in and a crashing gimp core. But you are probably right. So the problem is most likely just an old plug-in leftover from an earlier gimp-1.3 installation.
*** This bug has been marked as a duplicate of 126742 ***