Re: problems with windows gimp
On Wednesday, 17 Jan 2001, Nick Lamb wrote: > On Thu, Jan 18, 2001 at 12:42:23AM +0200, Tor Lillqvist wrote: > > (No, I don't know why duplicate PDB procedures cause strange errors > > and not just warnings. Anyway, GIMP seems to handle this situation > > better in the current gimp-1-2.) > > It's a long standing bug in Gimp. I would really like to change the name > of one of my plug-ins, but this bug prevents that (it would crash Gimp) > It's possible, but unlikely that it's actually fixed in 1.2.0, but > generally people poke inside the PDB, throw up, tweak something until > the crash that annoyed them stops and go home. > I don't blame them, and I wouldn't volunteer to re-write its hairy > logic, so I've stopped whining about it. (unless this counts :) ) I fixed a number of duplicate-name related leaks and memory trampling and other misc bugs in the PDB code a while back. I thought I'd caught most problems with duplicate names. If there are still problems remaining, then it would be good to know. Austin
Re: problems with windows gimp
Hi, Nick Lamb <[EMAIL PROTECTED]> writes: > On Thu, Jan 18, 2001 at 12:42:23AM +0200, Tor Lillqvist wrote: > > (No, I don't know why duplicate PDB procedures cause strange errors > > and not just warnings. Anyway, GIMP seems to handle this situation > > better in the current gimp-1-2.) > > It's a long standing bug in Gimp. I would really like to change the name > of one of my plug-ins, but this bug prevents that (it would crash Gimp) > It's possible, but unlikely that it's actually fixed in 1.2.0, but > generally people poke inside the PDB, throw up, tweak something until > the crash that annoyed them stops and go home. > I don't blame them, and I wouldn't volunteer to re-write its hairy > logic, so I've stopped whining about it. (unless this counts :) ) Oh, you better would have whined louder and submitted a bug-report. I just stumpled across this issue by accident and added a few checks for NULL pointers after 1.2.0 was out. 1.2.1 should behave better because of this, but I'm sure the problem wouldn't have existed in 1.2.0 if there would have been a proper bug-report earlier. A quick test (creating a copy of one plug-in in the plug-in path) makes me think that the problem is fixed in the current gimp-1-2 branch in CVS, but it would be nice if people could test it a little more. Salut, Sven
Re: problems with windows gimp
On Thu, Jan 18, 2001 at 12:42:23AM +0200, Tor Lillqvist wrote: > (No, I don't know why duplicate PDB procedures cause strange errors > and not just warnings. Anyway, GIMP seems to handle this situation > better in the current gimp-1-2.) It's a long standing bug in Gimp. I would really like to change the name of one of my plug-ins, but this bug prevents that (it would crash Gimp) It's possible, but unlikely that it's actually fixed in 1.2.0, but generally people poke inside the PDB, throw up, tweak something until the crash that annoyed them stops and go home. I don't blame them, and I wouldn't volunteer to re-write its hairy logic, so I've stopped whining about it. (unless this counts :) ) Nick.
problems with windows gimp
[EMAIL PROTECTED] writes: > Below is the error message i get, if there is a quick resolve to this > problem then please direct me to the proper online documentation, Remove either tiff_nolzw.exe of tiff.exe from your GIMP plug-ins directory. This is explained, perhaps a bit vaguely, on www.gimp.org/win32/ . (No, I don't know why duplicate PDB procedures cause strange errors and not just warnings. Anyway, GIMP seems to handle this situation better in the current gimp-1-2.) --tml
problems with windows gimp
To Whom It May Concern, I am a 3D animation student attempting to use your Win version of Gimp. I have used it in the past with Linux and love the program. I have installed about 4 times now, and keep running into the same error. Can you please help me??? Below is the error message i get, if there is a quick resolve to this problem then please direct me to the proper online documentation, otherwise if this is an unknown problem then i hope that this has now been brought to your attention. Steven Cochrane Gimp-WARNING **: removing duplicate PDB procedure "file_tiff_save" Gimp-WARNING **: removing duplicate PDB procedure "file_tiff_load" Glib-CRITICAL **: file gutils.c: line 393 (g_basename): assertion 'file_name ! = NULL' failed Gtk-CRITICAL **: file gtkitemfactory.c: line619 (gtk_item_factory_from_path): a ssertion 'path ! = NULL' failed Gimp-WARNING **: entry refers to unknown item factory: "(null)"