-
Notifications
You must be signed in to change notification settings - Fork 144
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
Gimp 3 support #78
Comments
OS: Arch Linux |
To expand a little bit on the previous comment for non-Arch users: on Debian I have installed GIMP 2.99.14 (debian
Gimp starts and the UI is PhotoGIMP'ed but will emit warnings because apparently the plug-ins that PhotoGIMP installs are in the wrong place, so I followed the warning suggestions and moved them. The plugins structure now looks like (not sure if it makes sense, I'm no GIMP expert):
Now at least on my debian bookworm GIMP 2.99 will complain onstartup (for each plugin):
I guess I'll investigate a bit more and test if Gimp 2.99 works for real (besides starting) hth |
Tumbleweed 2.99.15+git146.d087c1a84 |
GIMP 3.0 RC1 has been released (blog post): would be cool if someone that subscribed this issue could help and test PhotoGimp again (I might do it myself but just not quite soon). |
@Diolinux: Gimp 3.0 RC1 has been released: Linked to: |
I took some time to test PhotoGIMP with Gimp 3.0 RC1. Since I don't use flatpack I used the instructions posted in my previous comment. Here some new warnings on plug-ins I don't think I noticed before: Warning on gimprc value 'u8-gamma'
Note: unsure what is that for (code). Gimp will automatically remove it from the config (and backup the original gimprc). The warning will just disappear. A few plugins in PhotoGimp are brokenThese plugins:
Will fail with the same error because linked to libgimp 2.0
I didn't investigate further. A number of other plug-ins won't work but I think that's not relevant to PhotoGimp |
@Diolinux: Gimp 3.0 RC2 has been released: |
Is this PhotoGimp is ready for Gimp 3 (or 2.99) ?
The text was updated successfully, but these errors were encountered: