Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
python-fu doesn't work, childprocess doesn't fit
#2
Gimp keeps track of the plugins in the "pluginrc" file (which for you should be in  "C:\Users\Michael\.gimp-2.8\pluginrc". This is a plain text file and you can check the contents with a text editor.

Normally, on startup, Gimp checks the various "plugins" directories (those listed in Edit>Preferences>Folders>Plugins), and makes a list of all executables it finds there, with their last modification date. In parallel it re-reads the "pluginrc" file and makes a list of all the currently registered files, with their timestamps. Then it compares the lists:
  • Files in the directories that are already in "pluginrc" with the same timestamp are kept in pluginrc
  • Files in the directories that are already in "pluginrc" but with an older timestamp are re-registered
  • Files in the directories that are not in "pluginrc" are  registered
  • Files in pluginrc that are not found in the directories are silently dropped
Then the "pluginrc" file is saved.

All this means that if you get the message, Gimp is trying to execute a file that doesn't exist, but in that case it would have been removed from "pluginrc" by the startup registration process. The only explanation I have is that your pluginrc file is read-only and cannot be updated. A more exotic explanation is that there is a non-visible character somewhere (non-breaking space or such) that make the file name be handled differently by different pieces of the code.

So, are your plugins listed in pluginrc? Can you post your pluginrc file (Zip and add as attachment) or put it on some server (DropBox or else) and PM me the URL)?
Reply


Messages In This Thread
RE: python-fu doesn't work, childprocess doesn't fit - by Ofnuts - 08-09-2017, 09:42 AM
Problem solved!!!! - by gutschy - 08-09-2017, 04:14 PM

Forum Jump: