-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins install but fail in GIMP 2.99.12 on Windows 10 #52
Comments
Any solution on this topic? Facing the same issue... |
were you able to resolve it? The obvious problem seems to be that the path You need to manually change it to your PC OS user path. |
This seems not to be the problem. |
got it. Yes, unless the stable release comes, it will be problematic. Does it use the Gimp API? Seems exciting. Hopefully the developer will be patient with these changes. |
how to fix this os.path hardcoded issue ? |
I managed to get GIMP-ML installed in GIMP 2.99.12 on Windows 10. The weights were downloaded and installed manually.
The plugins load and appear in the layers menu but fail upon first use. I tried several of the plugins with similar results, here is the debug output for the deblur and superresolution plugins:
Traceback (most recent call last):
File "C:\GIMP-ML\gimpml\plugins\deblur\deblur.py", line 172, in run
result = deblur(
File "C:\GIMP-ML\gimpml\plugins\deblur\deblur.py", line 58, in deblur
with open(os.path.join(weight_path, "..", "gimp_ml_run.pkl"), "wb") as file:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Kritik Soman\GIMP-ML\weights\..\gimp_ml_run.pkl'
(deblur.py:6540): LibGimp-WARNING **: 01:13:10.440: gimp_procedure_run: no return values, shouldn't happen
C:\GIMP-ML\gimpml\plugins\deblur\deblur.py:232: Warning: g_error_new: assertion 'domain != 0' failed
Gimp.main(Deblur.gtype, sys.argv)
gimp_plug_in_destroy_proxies: ERROR: GimpImage proxy with ID 2 was refed by plug-in, it MUST NOT do that!
gimp_plug_in_destroy_proxies: ERROR: GimpLayer proxy with ID 22 was refed by plug-in, it MUST NOT do that!
The modal dialog message was the same for both attempts: Calling error for procedure 'file-png-save':
Could not open 'C:\Users\Kritik Soman\GIMP-ML\cache.png' for writing: No such file or directory
The text was updated successfully, but these errors were encountered: