GNOME Bugzilla – Bug 133490
CRITICAL message at start-up while parsing plug_in_rc
Last modified: 2004-12-22 21:47:04 UTC
Hi, When I deleted my ~/.gimp-1.3 this morning to do a test, and started up the GIMP, I got this message: (gimp-1.3:8859): Gimp-Config-CRITICAL **: file gimpconfigwriter.c: line 96 (gimp_config_writer_new_file): assertion 'error == NULL || *error == NULL' failed GIMP: Could not open '/home/dave/.gimp-1.3/pluginrc' for reading: No such file or directory. After digging about it turns out that gimp_scanner_new_file() returns NULL if it fails to find a scanner (which is reasonable), and sets the GError appropriately, but then plug_in_rc_parse() returns TRUE (success) and doesn't reset the error, so the assertion fails a little further on in plug_ins_init() (which is where we find it). I'm opening a bug because I'm not sure about the patch, and someone else I asked has been unable to reproduce the error. Dave.
Created attachment 24089 [details] [review] Patch to clear error after a first pass doesn't find any file
*** Bug 133480 has been marked as a duplicate of this bug. ***
bug confirmed by reporter of duplicate, I'll commit later. Dave.
Please see my comments on bug #133480 and redo your patch accordingly.
Putting this on the 2.0 milestone. This might get done today, but it might not. I'm pretty busy. Dave.
Since Bolsh said that he's away for a week, I've committed a fix to CVS instead: 2004-02-08 Sven Neumann <sven@gimp.org> * app/plug-in/plug-in-rc.c (plug_in_rc_parse): return FALSE if the file wasn't found. * app/plug-in/plug-ins.c (plug_ins_init): don't output the error message from plug_in_rc_parse() if it failed for file not found. Fixes bug #133490.