From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Using text tool in gimp causes seg fault
Date: Sat, 24 Sep 2022 17:58:01 +0200 [thread overview]
Message-ID: <20220924155801.F1uKotWmtJQunZpAiv3ghB7hjU8L1e2ReJYbRVK79sg@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: 1896 bytes --]
New comment by bugcrazy on void-packages repository
https://github.com/void-linux/void-packages/issues/39393#issuecomment-1253763967
Comment:
> > I reported issue/bug in glib gitlab https://gitlab.gnome.org/GNOME/glib/-/issues/2762 , but for team dev, there is no problem, for them issue/bug or any change that causes errors, it is a feature, they do not assume problems in the code, nor did they mention the failure in gimp
>
> So it's a bug in Gimp, obviously a bug report in glib will be closed if it's not a bug in glib.
>
> > It is a pesimous sign, projects connected to gnome, only care about gnome, make more problems, than solutions, this is the "gnome pattern".
>
> What do you mean? This is wrong and not even true, Gimp is maintained under GNOME.
>
> This is just standard software development, sometimes the bug is in a project expecting wrong behaviour, not in the library that fixes that.
On the FSF website, it states that Gnome Project is part of the GNU project, on the Gnome website, it says it is not part of the GNU project, on the Gimp website, it is part of the GNU project, but Gimp devs , they say no. The FSF and Gnome project are schizophrenic.
In this link dev Gnome, falls into contradiction, cannot explain, the inexplicable, when confronted, then closed the tropic, if not even the devs of Gnome, know their projects, imagine the problems, which are created!
https://discourse.gnome.org/t/relation-between-gimp-and-gnome/2376
https://www.gimp.org/develop/
Problems arise in the pre-launch 2.73 version, did not fix bugs and did not test, yet they released 2.74, other software like Gimp or not, are affected, not flaws or bugs of these projects, because in version 2.72, did not have this problem, The problem solution in version 2.74 is to go back to version 2.72. Soon more cases will arise, about the problems in version 2.74, wait.
next prev parent reply other threads:[~2022-09-24 15:58 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 ` [ISSUE] [CLOSED] " lxlml
2022-09-20 18:12 ` 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
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 [this message]
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=20220924155801.F1uKotWmtJQunZpAiv3ghB7hjU8L1e2ReJYbRVK79sg@z \
--to=paper42@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).