I spend hours trying to fix this stupid error and nothing work, please help

  • @thann
    link
    English
    8
    edit-2
    9 hours ago

    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

    • @[email protected]OP
      link
      fedilink
      19 hours ago

      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?

      • @thann
        link
        English
        49 hours ago

        Its been a bit of a schism lol

  • Strit
    link
    fedilink
    2213 hours ago

    I don’t see any errors, just warnings. And GTK is very verbose about warnings…

    • @thann
      link
      English
      69 hours ago

      There’s a segfault in the middle lol

    • @[email protected]OP
      link
      fedilink
      2
      edit-2
      13 hours ago

      The app run fine but ui are mass up and unusable became 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

      • Strit
        link
        fedilink
        1613 hours 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.

          • @woelkchen
            link
            1312 hours ago

            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.

          • data1701d (He/Him)
            link
            fedilink
            English
            812 hours ago

            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.

          • Strit
            link
            fedilink
            313 hours ago

            They tend to use different theming engines each major version, so I don’t believe they are.

  • data1701d (He/Him)
    link
    fedilink
    English
    813 hours ago

    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.so error). Maybe try reinstalling it with Pacman. Did you update your system and it somehow got autoremoved (I don’t know Arch that well)?

    • @[email protected]OP
      link
      fedilink
      112 hours ago

      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)

  • Gianluca
    link
    fedilink
    2
    edit-2
    13 hours ago

    @ColdWater I wouldn’t say its GTK fault. Reinstall ghostscript. gimp Is complaining about the postscript plugin that cant start

    • @[email protected]OP
      link
      fedilink
      212 hours ago

      I reinstall ghostscript and it’s doesn’t throw missing engine error anymore but it crash if I try to change theme (segmentation fault)

        • @PushButton
          link
          110 hours ago

          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.