all 5 comments

sorted by: hot top controversial new old
[–] 1 point 1 month ago (4 children)
  • [–] 1 point 1 month ago (3 children)

    You can sure mention bugs here and we can discuss it, but I doubt any developers are actually watching this community. Reporting a bug here is not the right way to actually request that a developer resolves it.

    I like to use PieFed to discuss software bugs with other users to determine if it is actually a valid problem and worth posting a formal issue report on their git repo or whatever.

    This seems to be the formal way to report bugs for this project: https://www.gimp.org/bugs/

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 month ago (2 children)

    I meant for the recent updates like 3.2.5. The issues there are all very old.

    It also doesn't work for me, I just see the "Create Issue" button loading continuously, can't get passed the first step.

    I'm not creating an account, so unless I see an error about requiring an account there, I won't make one.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 month ago* (1 child)

    I meant for the recent updates like 3.2.5. The issues there are all very old.

    It also doesn't work for me, I just see the "Create Issue" button loading continuously, can't get passed the first step.

    Where do you see that? I see how that website leads to their Gitlab instance.

    https://gitlab.gnome.org/GNOME/gimp/-/work_items

    Of the items there which are actually tagged with a version number, they are all recent versions:

    I'm not creating an account, so unless I see an error about requiring an account there, I won't make one.

    That is certainly a concern with formal bug reporting for any software project. It requires you to create an account with whatever git service that the project uses (GitHub, Codeberg, Gitlab, etc.).

  • source
  • parent
  • hideshow 1 child comment