From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Using text tool in gimp causes seg fault
Date: Wed, 21 Sep 2022 09:01:19 +0200 [thread overview]
Message-ID: <20220921070119.AdpoW420UER2rpId7JBCh43ocbx00SsDnPnl-pWF8BU@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: 1624 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39393#issuecomment-1253262508
Comment:
> nor did they mention the failure in gimp
Maybe he didn't see it? Or maybe he didn't want to comment on it due to the lack of information and the unfocused nature of the your issue. There's bug report for it on the gimp gitlab so hopefully someone can figure out where the issue is coming from and if it should be fixed in gimp or glib.
> for them issue/bug or any change that causes errors, it is a feature
I don't see anything wrong with what ebassi said.
Sometimes applications need to be updated to fix issues with improper/deprecated usage of their libraries, this isn't a gnome-specific thing. Especially with major version updates (such as in this case). If you are curious, you can find discussions between other developers in other issue threads about rationale behind some of the changes. (i.e. the `g_log_set_writer_func()` change)
As far as the chromium issues, afaik no one else can reproduce it (I certainly can't). You can always try making a new user account and then try opening chromium there to see if it is triggered by some of your settings?
> The indicated is to keep Glib 2.72 to fix.
Probably, at least, until the individual issues are resolved upstream either in glib or in the applications using glib (depending on the specific issue) in which case we would either import the patches or wait for a new release.
Edit: regarding the glib issue, here is a better issue thread for it:
https://gitlab.gnome.org/GNOME/gimp/-/issues/8576
next prev parent reply other threads:[~2022-09-21 7:01 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 [this message]
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
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=20220921070119.AdpoW420UER2rpId7JBCh43ocbx00SsDnPnl-pWF8BU@z \
--to=oreo639@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).