At the G’MIC command line, I can simulate some aspects of @pypedreams error message thus:
$ gmic -debug 0,0
[gmic]-0./ Start G'MIC interpreter (in debug mode).<gmic>-0./ Initial command line: 'cli_start , -debug 0,0'.
<gmic>./ Decompose command line into 4 items:
<gmic>./ item[0] = 'cli_start'
<gmic>./ item[1] = ','
<gmic>./ item[2] = '-debug'
<gmic>./ item[3] = '0,0'
<gmic>-0./ Enter scope './'.
<gmic>-0./ Item[0]: 'cli_start', selection [].
<gmic>-0./ Found custom command 'cli_start: ' (takes no arguments).
<gmic>-0./ Expand command line for command 'cli_start' to: ''.
<gmic>-0./cli_start/ Return from empty command 'cli_start/'.
<gmic>-0./ Item[2]: '-debug' -> 'debug', selection [].
<gmic>-0./ Item[3]: '0,0', selection [].
<gmic>-0./ Command 'input': arguments = '0,0'.
[gmic]-0./ Input file '0' at position 0
[gmic]-0./ *** Error *** Command 'input': File '0', format does not take any input options (options '0' specified).
In English: G’MIC, when it cannot designate any incoming item as a command, punts and assumes the presence of an implicit input command; the next item in the stream is taken to be an argument list to input
. In the simulation, the next item is taken to be an argument list: 0,0
. The first argument, 0
plays: to the input command, this calls for the creation of an empty image (image metadata without image data, useful for some purposes) This particular image format does not take image format options, which is what the second argument, also 0
, purports to be. Having been given an input option for a format that does not take any, G’MIC throws the observed exception.
My suspicions run along the lines that this event introduced nonsense into your gmic_qt_faves.json. Normally gimp/gmic_qt manages the content of this file without user intervention, so that filter settings may conveniently persist from use to use. Of course nonsense, if it gets in there, persists as well, which, to me, explains that the Mandelbrot filter no longer seems to work. The nonsense so introduced has, in part, put in place a pair of zeros separated by a comma — and maybe more, and is being taken as an argument list to an implicit input
command. If this theory of mine has any legs, then moving/renaming/deleting this possibly corrupt .json
file should cure the problem — and delete all of these conveniently kept and possibly corrupt settings. See the GimpChat discussion linked in above for particulars of finding this file. Being a .json
file, you can look at it with a text editor and, perhaps, find the nonsense that is the source of your difficulty.
Let us know if this works out.