I spend hours trying to fix this stupid error and nothing work, please help
@ColdWater I wouldn’t say its GTK fault. Reinstall ghostscript. gimp Is complaining about the postscript plugin that cant start
I reinstall ghostscript and it’s doesn’t throw missing engine error anymore but it crash if I try to change theme (segmentation fault)
Rewrite it in Rust!
/s
Imagine the amount of dependencies for a project like that… That would fix the seg fault memory issue, but only to end up with an out of HD space issue.
You may need gtk-murrine-engine (actual package name may differ).
(completely sidetracked here – there’s a reason Dirk Hohndel (and Linus) decided to go with Qt instead of GTK)
The additional compilation overhead is a good stress test for a new kernel? /j
Why are you running gimp as root lol?
Also they’ve been working on upgrading to gtk3 for a decade so hopefully that fixes everything
I’m not, I just run it through terminal too see what’s going on, and seriously a decade? And it’s still not complete?
Its been a bit of a schism lol
I don’t see any errors, just warnings. And GTK is very verbose about warnings…
The app run fine but ui are mass up and unusable because of missing themes engines, and it crash (I got segmentation fault) if I try to change theme to system theme it’s fine 3 days ago
Gimp is likely still using gtk2, which means you need a theme that supports gtk2. That’s probably old and un-maintained, since gtk2 has been End-Of-Life for a while now. gimp 3.0 is approaching though.
Is gtk not backward compatible with older version?
They tend to use different theming engines each major version, so I don’t believe they are.
Is gtk not backward compatible with older version?
New main versions of software usually is not compatible with old versions. That’s one of the points of new main versions. You cannot load Qt 3 themes into Qt 6 either.
Additionally, I think 3.18 onward doesn’t even support theming engines. As said, though, GIMP is stuck on GTK2.
If you’re having a lot of trouble, perhaps just go with the Flatpak.
No. GTK 3 was a breaking change, and so was 4.
There’s a segfault in the middle lol
Please specify:
- What distribution
- What architecture
- What desktop environment
- What you have done so far to try to resolve the problem (e.g have you tried uninstalling and reinstalling the package?)
Based on your host name, I’m assuming it’s Arch. From what I can tell from the terminal output, Ghostscript is missing (thus the
libgs.soerror). Maybe try reinstalling it with Pacman. Did you update your system and it somehow got autoremoved (I don’t know Arch that well)?I installed ghostscript and it doesn’t give me error anymore but it still crash if I try to change theme
(script-fu:2516): LibGimpBase-WARNING **: 14:13:54.547: script-fu: gimp_wire_read(): error Segmentation fault (core dumped)What themes do you have installed, and which theme are you trying to switch to? Also, can you confirm what distro and DE you’re using as well as any major customizations so I can try and replicate the problem in an Arch VM, please?
Hi, it’s Arch Linux and for gtk application style it’s “Materia-Blackout”, I don’t have any major customization except I hide title bar in “Breeze Window Decoration” I set “Window-Specific Overrides” to “.*” and tick “Hide Window title bar” I also use global menu and “Application title bar” widget
