GNOME Bugzilla – Bug 125954
gimp 1.3.21 fails to start when -s flag is attached on FreeBSD STABLE and CURRENT
Last modified: 2003-11-01 02:45:54 UTC
GIMP won't start (abort trap) if the splash ommitting -s flag is set. The "ommit image splash only" -S flag doesn't have this effect Other user have reported to me that they also can observe this behaviour on their machines. I was testing it on 4.9 STABLE on a generic desktop PC and on 5.1 RELEASE on Thinkpad 600e. The debug log message below comes from the PC (AMD CPU). This is windowing environment independent (appeared both in twm and GNOME 2.4) GIMP has been compiled with this options set: --enable-python --disable-perl --disable-print --disable-gtk-doc --with-html-dir=${PREFIX}/share/doc/gimp $ gimp-1.3 -s %U $ This is a development version of the GIMP Debug messages may appear here. Testing CPU features... mmx : yes 3dnow : yes mmxext : yes sse : no sse2 : no gimp_composite: use=yes, verbose=no +mmx +sse +3dnow Gimp-ERROR **: file app_procs.c: line 198 (app_init): assertion failed: (update_status_func != NULL) aborting... gimp-1.3: terminated: Abort trap
This has been fixed in CVS a while ago already: 2003-10-06 Michael Natterer <mitch@gimp.org> * app/app_procs.c (app_init): fixed starting with --no-splash.