From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Using text tool in gimp causes seg fault
Date: Wed, 21 Sep 2022 23:10:45 +0200 [thread overview]
Message-ID: <20220921211045.F4kHvHIGYYJYY85BXAIgDzpyhGGNHUWLeiLs0oEVZBA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39393@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
New comment by bugcrazy on void-packages repository
https://github.com/void-linux/void-packages/issues/39393#issuecomment-1254231763
Comment:
> > I prefer the opinion of the creator of OpenBSD about crashs in the gimp
>
> That's an unrelated issue. That issue thread has to do with memory limits, not the null pointer dereference.
>
> As stated to you in that thread, OpenBSD is using glib 2.72.4 (Just so you know, 2.73 is the unstable/testing branch for the 2.74 major version, and isn't supposed to be shipped in production). https://github.com/openbsd/ports/blob/master/devel/glib2/Makefile
This I know, I answered the questions, which were asked. Software development is not just a source code, there are people with their merits and failures.
Gimp has bugs, is the problem of devs Gimp, the same is for glib, but both projects are Gnome, so the devs are the same, so if problem is gimp, why back to glib 2.72, solves problem? If the problem is Gimp, not glib?
I updated glib 2.74, several software no longer started, I went back to glib 2.72, everything worked again, the applications are GTK, although Gimp has problems in the source code, glib 2.74 has problems too.
next prev parent reply other threads:[~2022-09-21 21:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 18:08 [ISSUE] " lxlml
2022-09-20 18:12 ` lxlml
2022-09-20 18:12 ` [ISSUE] [CLOSED] " lxlml
2022-09-20 18:15 ` lxlml
2022-09-20 18:42 ` lxlml
2022-09-20 18:57 ` paper42
2022-09-21 3:43 ` bugcrazy
2022-09-21 6:28 ` oreo639
2022-09-21 6:28 ` oreo639
2022-09-21 6:29 ` oreo639
2022-09-21 6:32 ` oreo639
2022-09-21 6:42 ` oreo639
2022-09-21 6:42 ` oreo639
2022-09-21 7:01 ` oreo639
2022-09-21 7:01 ` oreo639
2022-09-21 7:03 ` oreo639
2022-09-21 7:03 ` oreo639
2022-09-21 7:05 ` oreo639
2022-09-21 7:08 ` oreo639
2022-09-21 7:08 ` oreo639
2022-09-21 7:14 ` oreo639
2022-09-21 7:14 ` oreo639
2022-09-21 7:17 ` oreo639
2022-09-21 7:45 ` oreo639
2022-09-21 9:39 ` paper42
2022-09-21 10:32 ` biopsin
2022-09-21 14:06 ` bugcrazy
2022-09-21 14:25 ` biopsin
2022-09-21 14:26 ` biopsin
2022-09-21 14:26 ` paper42
2022-09-21 17:08 ` bugcrazy
2022-09-21 19:56 ` oreo639
2022-09-21 19:56 ` oreo639
2022-09-21 19:57 ` oreo639
2022-09-21 19:58 ` oreo639
2022-09-21 19:59 ` oreo639
2022-09-21 21:10 ` bugcrazy [this message]
2022-09-21 21:28 ` paper42
2022-09-21 21:31 ` paper42
2022-09-22 0:05 ` bugcrazy
2022-09-22 0:14 ` paper42
2022-09-24 15:57 ` paper42
2022-09-24 15:57 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-25 15:24 ` paper42
2022-09-26 16:38 ` [ISSUE] [CLOSED] " paper42
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220921211045.F4kHvHIGYYJYY85BXAIgDzpyhGGNHUWLeiLs0oEVZBA@z \
--to=bugcrazy@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).